Name: capi-controller-manager-bc4cf8c95-wbf5n Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.205 Start Time: Tue, 14 Apr 2026 13:17:59 +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.86 IPs: IP: 10.0.0.86 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://d0089477e2a55ddddb1e1760bb28cad7e950e6727f2b871d272d17b7079946b6 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: Tue, 14 Apr 2026 13:27:42 +0000 Last State: Terminated Reason: Error Message: 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0414 13:26:15.195278 1 controller.go:239] "Starting Controller" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0414 13:26:15.195289 1 controller.go:248] "Starting workers" controller="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=100 I0414 13:26:15.195483 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0414 13:26:15.195545 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 I0414 13:26:15.195706 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0414 13:26:15.195776 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 E0414 13:26:25.729792 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0414 13:26:30.730046 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 I0414 13:26:30.730111 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0414 13:26:30.730217 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 14 Apr 2026 13:25:56 +0000 Finished: Tue, 14 Apr 2026 13:26:53 +0000 Ready: True Restart Count: 3 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-wbf5n (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-qmflj (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-qmflj: 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 38m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-wbf5n to instance Warning Unhealthy 31m (x4 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.86:9440/healthz": dial tcp 10.0.0.86:9440: connect: connection refused Normal Killing 31m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 30m (x9 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.86:9440/readyz": dial tcp 10.0.0.86:9440: connect: connection refused Normal Pulled 30m (x3 over 38m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 30m (x3 over 38m) kubelet Created container manager Normal Started 30m (x3 over 38m) kubelet Started container manager Warning Unhealthy 29m kubelet Readiness probe failed: Get "http://10.0.0.86:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x2 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.86:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)