Closed taotriad closed 1 month ago
At the very least we need to double-check on upgrade whether any feature gates are enabled; upgrades may fail due to changes to gated features.
Most upgrade issues have been fixed as of f449d2990a4aff693b483ef4822ffce37ba3aadd in the systempath branch, but there's still no check that refuses to attempt an upgrade when feature gates are enabled.
a3a3b57b46d5baa35a8be24a2dbc89f93861efcd and 561247977fed8d0dd132692755bb8d2ec672a002 in the systempath branch should fix the remaining upgrade issues; upgrading from 1.30 to 1.31 has been verified to work, and upgrades when there are modified feature gates should be aborted unless the user explicitly overrides that check.
The systempath branch has been merged to the main branch.
Upgrading from Kubernetes v1.30 to v1.31 fails.
cmtadm upgrade-control-plane
Not only does the upgrade fail, but the cluster is no longer functional afterwards.
Making a clean installation of Kubernetes v1.31 using cmtadm works, so it seems to be something in the upgrade code that is incorrect (it could of course be an upstream issue).