Name: capi-controller-manager-bc4cf8c95-7r4sf Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.44 Start Time: Fri, 24 Apr 2026 07:01:45 +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.43 IPs: IP: 10.0.0.43 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://eb57dbfcb22c6ad1c9564f63f7d5b6bb81c4a9b2752341040138097bbdc2ba8a 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, 24 Apr 2026 07:08:40 +0000 Last State: Terminated Reason: Error Message: "cluster.x-k8s.io" controllerKind="ClusterClass" worker count=10 E0424 07:08:18.791584 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 E0424 07:08:23.787966 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 I0424 07:08:23.788036 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded I0424 07:08:23.788128 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-7r4sf_99ae29f1-2bde-4398-8e52-11160065c3e3 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"dced95af-5c71-48de-b7bd-39973294c669","apiVersion":"coordination.k8s.io/v1","resourceVersion":"17534"} reason="LeaderElection" I0424 07:08:23.788226 1 internal.go:538] "Stopping and waiting for non leader election runnables" I0424 07:08:23.788249 1 internal.go:542] "Stopping and waiting for leader election runnables" I0424 07:08:23.788284 1 internal.go:550] "Stopping and waiting for caches" I0424 07:08:23.788302 1 internal.go:554] "Stopping and waiting for webhooks" I0424 07:08:23.788310 1 internal.go:557] "Stopping and waiting for HTTP servers" I0424 07:08:23.788321 1 internal.go:561] "Wait completed, proceeding to shutdown the manager" E0424 07:08:23.788327 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" I0424 07:08:23.788362 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" Exit Code: 1 Started: Fri, 24 Apr 2026 07:07:07 +0000 Finished: Fri, 24 Apr 2026 07:08:23 +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-7r4sf (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-lzklk (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-lzklk: 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 27m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-7r4sf to instance Normal Started 23m (x2 over 27m) kubelet Started container manager Warning Unhealthy 22m (x6 over 24m) kubelet Liveness probe failed: Get "http://10.0.0.43:9440/healthz": dial tcp 10.0.0.43:9440: connect: connection refused Warning Unhealthy 22m (x10 over 24m) kubelet Readiness probe failed: Get "http://10.0.0.43:9440/readyz": dial tcp 10.0.0.43:9440: connect: connection refused Normal Killing 22m (x2 over 23m) kubelet Container manager failed liveness probe, will be restarted Normal Pulled 22m (x3 over 27m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 22m (x3 over 27m) kubelet Created container manager