generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Description
The node-readiness-controller shouldn't be blocked by node taints creating a possible deadlock if the taints were not properly managed in the cluster. Also, currently the controller deployment targets control-plane nodes as default, for default-behavior 'any available node' works better.
- Remove
nodeSelectorfor controller (manager) deployment inconfig/manager/manager.yaml - Add broad tolerations for the deployment., ie:
spec:
template:
spec:
tolerations:
- operator: Exists
effect: NoSchedule
- operator: Exists
effect: NoExecuteIn the future this could be replaced with tolerate only readiness.k8s.io/* taints specifically, but that's need wildcard support in K8s.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.