etcd 3.4 with auth enabled, can it perform a rolling upgrade to version 3.5 after disable auth？

[waxihus]

For etcd 3.4 with authentication enabled, can it perform a rolling upgrade to version 3.5 after disabling authentication and deleting user before the upgrade? Or, are there other methods to upgrade to 3.5 while keeping authentication enabled? Are there any considerations?

in Upgrade etcd from 3.4 to 3.5：
NOTE: If your cluster enables auth, rolling upgrade from 3.4 or older version isn’t supported because 3.5 changes a format of WAL entries related to auth.