Name: capi-controller-manager-bc4cf8c95-6n5b5 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.25 Start Time: Fri, 17 Apr 2026 11:37:08 +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.112 IPs: IP: 10.0.0.112 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://53024e479b313d5630841495db6600710e5499806eec3b53dec7c7202cb803dd 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: Fri, 17 Apr 2026 11:44:18 +0000 Last State: Terminated Reason: Error Message: Group="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0417 11:42:04.912061 1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0417 11:42:04.912122 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0417 11:42:04.912140 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0417 11:42:04.912119 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 E0417 11:42:27.956709 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 E0417 11:42:32.956868 1 leaderelection.go:472] Failed to update lock: 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 I0417 11:42:32.956973 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0417 11:42:32.957570 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" I0417 11:42:32.957614 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-6n5b5_a907ad2c-757c-4545-9ac1-9f61a83551b9 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"e3be93fb-2e09-4261-9ddf-0c2e5f2d4dce","apiVersion":"coordination.k8s.io/v1","resourceVersion":"24014"} reason="LeaderElection" Exit Code: 1 Started: Fri, 17 Apr 2026 11:41:42 +0000 Finished: Fri, 17 Apr 2026 11:43:04 +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-6n5b5 (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-4hkbc (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-4hkbc: 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 19m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-6n5b5 to instance Normal Pulled 14m (x2 over 19m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 14m (x3 over 15m) kubelet Liveness probe failed: Get "http://10.0.0.112:9440/healthz": dial tcp 10.0.0.112:9440: connect: connection refused Normal Created 14m (x2 over 19m) kubelet Created container manager Normal Started 14m (x2 over 19m) kubelet Started container manager Normal Killing 13m (x2 over 14m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 13m (x3 over 13m) kubelet Liveness probe failed: Get "http://10.0.0.112:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 13m (x3 over 13m) kubelet Readiness probe failed: Get "http://10.0.0.112:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 12m (x9 over 15m) kubelet Readiness probe failed: Get "http://10.0.0.112:9440/readyz": dial tcp 10.0.0.112:9440: connect: connection refused