Skip to content

Update manager.yaml to modify nodeSelector and tolerations #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rohitkbc wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −4
Open

Update manager.yaml to modify nodeSelector and tolerations #129

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d4ff2cc
Update manager.yaml to modify nodeSelector and tolerations
rohitkbc Feb 12, 2026
644d4c8
Update config/manager/manager.yaml
ajaysundark Mar 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions config/manager/manager.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,13 @@ spec:
# values:
# - platform # Modify this value based on your platform node labels.
priorityClassName: system-cluster-critical
nodeSelector:
"node-role.kubernetes.io/control-plane": ""
# TODO: In the future, this could be replaced with tolerate only readiness.k8s.io/* taints specifically, when wildcard support is available in K8s.
# (ref: https://github.com/kubernetes/enhancements/issues/5500)
tolerations:
- key: "node-role.kubernetes.io/control-plane"
operator: "Exists"
- operator: Exists
effect: NoSchedule
- operator: Exists
effect: NoExecute
securityContext:
# Projects are configured by default to adhere to the "restricted" Pod Security Standards.
# This ensures that deployments meet the highest security requirements for Kubernetes.
Expand Down