Name: capi-controller-manager-bc4cf8c95-8pr9v Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.240 Start Time: Tue, 12 May 2026 12:27:05 +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.92 IPs: IP: 10.0.0.92 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://bbe46953f7d3174387f71ae5faa8f4b031fa888ef42ed1041f2aed3bc0e01556 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, 12 May 2026 12:36:14 +0000 Last State: Terminated Reason: Error Message: Get "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:01.745356 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": dial tcp 10.96.0.1:443: connect: connection refused, falling back to slow path E0512 12:34:01.746009 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": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:03.740832 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": dial tcp 10.96.0.1:443: connect: connection refused, falling back to slow path E0512 12:34:03.741403 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": dial tcp 10.96.0.1:443: connect: connection refused E0512 12:34:05.739788 1 leaderelection.go:429] Failed to update lock optimistically: client rate limiter Wait returned an error: context deadline exceeded, falling back to slow path E0512 12:34:05.739844 1 leaderelection.go:436] error retrieving resource lock capi-system/controller-leader-election-capi: client rate limiter Wait returned an error: context deadline exceeded I0512 12:34:05.739863 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0512 12:34:05.739940 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 12 May 2026 12:32:11 +0000 Finished: Tue, 12 May 2026 12:36:02 +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-8pr9v (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-82qgz (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-82qgz: 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 40m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-8pr9v to instance Warning Unhealthy 36m (x3 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.92:9440/healthz": dial tcp 10.0.0.92:9440: connect: connection refused Normal Pulled 35m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 35m (x7 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.92:9440/readyz": dial tcp 10.0.0.92:9440: connect: connection refused Normal Created 35m (x2 over 40m) kubelet Created container manager Normal Started 35m (x2 over 40m) kubelet Started container manager Normal Killing 33m (x2 over 36m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 33m (x3 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.92:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x5 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.92:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)