Name: capi-controller-manager-bc4cf8c95-2bt5v Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/162.253.55.74 Start Time: Fri, 27 Feb 2026 02:02:43 +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.192 IPs: IP: 10.0.0.192 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://b519f2be65717c34a5aa8ffe73e7b345354848e03acfcd736c1f512a0407e651 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, 27 Feb 2026 02:08:43 +0000 Last State: Terminated Reason: Error Message: 227 02:07:36.902957 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0227 02:07:36.902963 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 E0227 02:07:50.720102 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, falling back to slow path E0227 02:07:55.720729 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) E0227 02:07:55.720904 1 leaderelection.go:429] Failed to update lock optimistically: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline, falling back to slow path E0227 02:07:55.720997 1 leaderelection.go:436] error retrieving resource lock capi-system/controller-leader-election-capi: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline I0227 02:07:55.721059 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0227 02:07:55.721157 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" I0227 02:07:55.721149 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-2bt5v_cf704d9c-6bea-4b17-9e43-a3edfdfea53e stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"c9f3f029-c257-427c-ba32-e97098b0feec","apiVersion":"coordination.k8s.io/v1","resourceVersion":"26943"} reason="LeaderElection" Exit Code: 1 Started: Fri, 27 Feb 2026 02:07:18 +0000 Finished: Fri, 27 Feb 2026 02:08:27 +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-2bt5v (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-8hpcz (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-8hpcz: 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 32m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-2bt5v to instance Warning Unhealthy 28m (x3 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.192:9440/healthz": dial tcp 10.0.0.192:9440: connect: connection refused Warning Unhealthy 27m (x8 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.192:9440/readyz": dial tcp 10.0.0.192:9440: connect: connection refused Normal Pulled 27m (x2 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 27m (x2 over 32m) kubelet Created container manager Normal Started 27m (x2 over 32m) kubelet Started container manager Normal Killing 26m (x2 over 28m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 26m (x3 over 27m) kubelet Liveness probe failed: Get "http://10.0.0.192:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 26m (x4 over 27m) kubelet Readiness probe failed: Get "http://10.0.0.192:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)