Name: capi-controller-manager-bc4cf8c95-rc797 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.250 Start Time: Mon, 27 Apr 2026 21:52:13 +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.183 IPs: IP: 10.0.0.183 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://928abee4b7e4f5c37010fb96f514893f81bb00b580889111933e5be764cea1ea 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: Mon, 27 Apr 2026 21:57:54 +0000 Last State: Terminated Reason: Error Message: ntroller.go:248] "Starting workers" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 E0427 21:57:07.631212 1 leaderelection.go:429] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capi), falling back to slow path E0427 21:57:09.635800 1 event.go:359] "Server rejected event (will not retry!)" err="etcdserver: request timed out" event="&Event{ObjectMeta:{controller-leader-election-capi.18aa5582a9910463 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:667a824d-aab2-4481-ac3f-d52106c80521,APIVersion:coordination.k8s.io/v1,ResourceVersion:26064,FieldPath:,},Reason:LeaderElection,Message:capi-controller-manager-bc4cf8c95-rc797_5a00ed07-7085-4a43-9dd1-4b7cd593a4fc became leader,Source:EventSource{Component:capi-controller-manager-bc4cf8c95-rc797_5a00ed07-7085-4a43-9dd1-4b7cd593a4fc,Host:,},FirstTimestamp:2026-04-27 21:57:02.630044771 +0000 UTC m=+33.301742706,LastTimestamp:2026-04-27 21:57:02.630044771 +0000 UTC m=+33.301742706,Count:1,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:capi-controller-manager-bc4cf8c95-rc797_5a00ed07-7085-4a43-9dd1-4b7cd593a4fc,ReportingInstance:,}" E0427 21:57:12.630769 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 I0427 21:57:12.630837 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0427 21:57:12.630935 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Mon, 27 Apr 2026 21:56:29 +0000 Finished: Mon, 27 Apr 2026 21:57:30 +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-rc797 (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-qt6fm (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-qt6fm: 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 35m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-rc797 to instance Normal Pulled 31m (x2 over 35m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 31m (x2 over 35m) kubelet Created container manager Normal Started 31m (x2 over 35m) kubelet Started container manager Warning Unhealthy 30m (x2 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.183:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m (x2 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.183:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m (x4 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.183:9440/healthz": dial tcp 10.0.0.183:9440: connect: connection refused Normal Killing 30m (x2 over 31m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 29m (x10 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.183:9440/readyz": dial tcp 10.0.0.183:9440: connect: connection refused