This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
Enable flagging a kubelet as a master node for tainting. #333
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 this PR does / why we need it:
This enables labeling and tainting on master nodes that wish to deploy a Kubelet. This is the foundation to enable pluggable CNI support in CFCR.
How can this PR be verified?
Deploy CFCR with a kubelet on the master node. The node should be labeled
node-role.kubernetes.io/master=
and taintednode-role.kubernetes.io/master=:NoSchedule
Is there any change in kubo-deployment?
Yes (forthcoming), an ops file that will deploy CFCR with kubelets on the master.
Is there any change in kubo-ci?
Yes (forthcoming), to test this variant of CFCR deployment.
Does this affect upgrade, or is there any migration required?
No, though future capabilities that build on this may (e.g. pluggable CNIs).
Which issue(s) this PR fixes:
N/A
Release note: