Name: capi-controller-manager-bc4cf8c95-2gztv Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.153 Start Time: Fri, 27 Feb 2026 02:11:27 +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.188 IPs: IP: 10.0.0.188 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://2b87090c08dda43fef2992d53d5c951c0124a793a9a53a90abd31813e6e5a191 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:17:34 +0000 Last State: Terminated Reason: Error Message: eded while awaiting headers), falling back to slow path E0227 02:16:16.234895 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{controller-leader-election-capi.1897f8d454765579 capi-system 0 0001-01-01 00:00:00 +0000 UTC map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Lease,Namespace:capi-system,Name:controller-leader-election-capi,UID:072bf402-e48a-4f39-83f8-010476010ab1,APIVersion:coordination.k8s.io/v1,ResourceVersion:24094,FieldPath:,},Reason:LeaderElection,Message:capi-controller-manager-bc4cf8c95-2gztv_0dc2203f-d8e1-44d4-b904-8c02711d4dfa became leader,Source:EventSource{Component:capi-controller-manager-bc4cf8c95-2gztv_0dc2203f-d8e1-44d4-b904-8c02711d4dfa,Host:,},FirstTimestamp:2026-02-27 02:16:09.227375993 +0000 UTC m=+24.916981543,LastTimestamp:2026-02-27 02:16:09.227375993 +0000 UTC m=+24.916981543,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:capi-controller-manager-bc4cf8c95-2gztv_0dc2203f-d8e1-44d4-b904-8c02711d4dfa,ReportingInstance:,}" E0227 02:16:33.582502 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 E0227 02:16:38.582944 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) I0227 02:16:38.583180 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0227 02:16:38.583320 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 27 Feb 2026 02:15:44 +0000 Finished: Fri, 27 Feb 2026 02:16:38 +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-2gztv (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-zsrw6 (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-zsrw6: 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 31m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-2gztv to instance Normal Started 27m (x2 over 31m) kubelet Started container manager Warning Unhealthy 26m (x6 over 27m) kubelet Liveness probe failed: Get "http://10.0.0.188:9440/healthz": dial tcp 10.0.0.188:9440: connect: connection refused Normal Killing 26m (x2 over 27m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 25m (x10 over 27m) kubelet Readiness probe failed: Get "http://10.0.0.188:9440/readyz": dial tcp 10.0.0.188:9440: connect: connection refused Normal Pulled 25m (x3 over 31m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 25m (x3 over 31m) kubelet Created container manager