-
Notifications
You must be signed in to change notification settings - Fork 110
Description
TL;DR
The hcloud-csi-node DaemonSet in deploy/kubernetes/hcloud-csi.yml includes tolerations, but the hcloud-csi-controller Deployment doesnt.
This causes the controller to fail scheduling in clusters where control-plane nodes are tainted by default.
I am using version 2.18.3, but the problem still exists in 2.19.1
Expected behavior
kubectl get pods -n kube-system | grep csi
hcloud-csi-controller-xxxxxxxxx-xxxxx 5/5 Running 0 5m
hcloud-csi-node-xxxxx 3/3 Running 0 5m
Observed behavior
kubectl get pods -n kube-system | grep csi
hcloud-csi-controller-xxxxxxxxx-xxxxx 0/5 Pending 0 5m
hcloud-csi-node-xxxxx 3/3 Running 0 5m
Minimal working example
Add the tolerations to the hcloud-csi-controller Deployment
tolerations:
- key: CriticalAddonsOnly
operator: ExistsLog output
Additional information
No response