Always update MachineDeployment to the indicated kubernetes version when --upgrade-machine-deployments is in use #3373
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
sig/cluster-management
Denotes a PR or issue as being assigned to SIG Cluster Management.
Comments
kron4eg
added
kind/feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the feature you would like to add / User story
Currently kubeone will update MachineDeployment to the configured kubernetes version ONLY if it's entering the upgrade path. Once control-plane is updated, this flag is NOOP. This is not documented, nether is intuitive.
Solution details
Instead, we should act on this flag regardless of which internal logic path has been chosen (init or refresh or upgrade). If the flag is given, MachineDeployments in the cluster should have configured version.
Use cases
The text was updated successfully, but these errors were encountered: