Replace node-role.kubernetes.io/master with control-plane label and add control-plane toleration #2017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
node-role.kubernetes.io/master
label selector withnode-role.kubernetes.io/control-plane
node-role.kubernetes.io/master
labelnode-role.kubernetes.io/control-plane
label, and since KubeOne 1.4 only supports Kubernetes 1.20 and newer, it's safe to do this migrationnode-role.kubernetes.io/control-plane
toleration in addition tonode-role.kubernetes.io/master
tolerationnode-role.kubernetes.io/master
toleration will be removed with Kubernetes 1.25Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):xref #2010
Does this PR introduce a user-facing change?:
/assign @kron4eg