Name: capi-controller-manager-bc4cf8c95-jw64k Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.244 Start Time: Thu, 11 Jun 2026 07:39:33 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=bc4cf8c95 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.240 IPs: IP: 10.0.0.240 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://1c80c157b0a0ce4ce91e4d39068bd1b8425dd2b0a34f0388df685a97bc8f3b18 Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller@sha256:d93407d031296336ccbabc8494005672dc048c4ebc616ccfc18f813d49bd87fc Ports: 9443/TCP, 9440/TCP, 8443/TCP Host Ports: 0/TCP, 0/TCP, 0/TCP Command: /manager Args: --leader-elect --diagnostics-address=:8443 --insecure-diagnostics=false --feature-gates=MachinePool=true,ClusterResourceSet=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=false State: Running Started: Thu, 11 Jun 2026 08:08:49 +0000 Last State: Terminated Reason: Error Message: ourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0611 07:45:06.696937 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0611 07:45:06.696970 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0611 07:45:06.696995 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0611 07:45:06.696976 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 I0611 07:45:06.697608 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0611 07:45:06.697643 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0611 08:07:45.993032 1 leaderelection.go:429] Failed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": context deadline exceeded (Client.Timeout exceeded while awaiting headers), falling back to slow path E0611 08:07:50.991840 1 leaderelection.go:436] error retrieving resource lock capi-system/controller-leader-election-capi: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": context deadline exceeded I0611 08:07:50.991907 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0611 08:07:50.992033 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 11 Jun 2026 07:44:47 +0000 Finished: Thu, 11 Jun 2026 08:08:15 +0000 Ready: True Restart Count: 2 Liveness: http-get http://:healthz/healthz delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:healthz/readyz delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: POD_NAMESPACE: capi-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-bc4cf8c95-jw64k (v1:metadata.name) POD_UID: (v1:metadata.uid) Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jj4ww (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capi-webhook-service-cert Optional: false kube-api-access-jj4ww: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: DownwardAPI: true QoS Class: BestEffort Node-Selectors: openstack-control-plane=enabled Tolerations: node-role.kubernetes.io/control-plane:NoSchedule node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 48m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-jw64k to instance Warning Unhealthy 44m (x3 over 44m) kubelet Liveness probe failed: Get "http://10.0.0.240:9440/healthz": dial tcp 10.0.0.240:9440: connect: connection refused Normal Pulled 43m (x2 over 48m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 43m (x11 over 44m) kubelet Readiness probe failed: Get "http://10.0.0.240:9440/readyz": dial tcp 10.0.0.240:9440: connect: connection refused Normal Killing 43m (x4 over 44m) kubelet Container manager failed liveness probe, will be restarted Normal Created 43m (x2 over 48m) kubelet Created container manager Normal Started 43m (x2 over 48m) kubelet Started container manager Warning Unhealthy 19m (x3 over 20m) kubelet Readiness probe failed: Get "http://10.0.0.240:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 19m (x3 over 20m) kubelet Liveness probe failed: Get "http://10.0.0.240:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)