From 45d760f06a53d5754bbe208959c8db3e997d09d1 Mon Sep 17 00:00:00 2001 From: nikolayzakharov Date: Thu, 20 Aug 2026 13:39:34 +0200 Subject: [PATCH] Tolerate uninitialized taint in CCM deployment Kubelet sets the taint node.cloudprovider.kubernetes.io/uninitialized on each node when it runs with --cloud-provider=external. The deployment has no tolerations block, so the scheduler cannot place the pod, and it stays Pending on a new cluster. Add a toleration for this taint only. The operator Exists matches the taint with any value. --- deploy/cloud-controller-manager/deployment.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/deploy/cloud-controller-manager/deployment.yaml b/deploy/cloud-controller-manager/deployment.yaml index 7de7422e..5f25a268 100644 --- a/deploy/cloud-controller-manager/deployment.yaml +++ b/deploy/cloud-controller-manager/deployment.yaml @@ -17,6 +17,10 @@ spec: labels: app: stackit-cloud-controller-manager spec: + tolerations: + - key: node.cloudprovider.kubernetes.io/uninitialized + operator: Exists + effect: NoSchedule serviceAccountName: stackit-cloud-controller-manager terminationGracePeriodSeconds: 30 containers: