Skip to content

fix(cert-manager): tolerate tainted unraid nodes #89

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

Merged
syscod3 merged 1 commit into from
Sep 8, 2026
Merged

fix(cert-manager): tolerate tainted unraid nodes #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
29 changes: 29 additions & 0 deletions values/base/cert-manager.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,31 @@
crds:
enabled: true

# Unraid-lab runs all nodes with NoSchedule taints: three control-plane nodes,
# plus the runner node taint on the first control-plane. Cert-manager must be
# schedulable on the cluster's only available nodes.
tolerations:
- key: node-role.kubernetes.io/control-plane
operator: Exists
effect: NoSchedule
- key: imp.dev/runner
operator: Exists
effect: NoSchedule

webhook:
tolerations:
- key: node-role.kubernetes.io/control-plane
operator: Exists
effect: NoSchedule
- key: imp.dev/runner
operator: Exists
effect: NoSchedule

cainjector:
tolerations:
- key: node-role.kubernetes.io/control-plane
operator: Exists
effect: NoSchedule
- key: imp.dev/runner
operator: Exists
effect: NoSchedule
Loading