Name: capi-controller-manager-bc4cf8c95-lft97 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.162 Start Time: Wed, 13 May 2026 19:14:19 +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.251 IPs: IP: 10.0.0.251 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://590f0e1762a2ea2fa3a2c2993de700a1fa1356f395bc224a0a383de63f61b9ed 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: Wed, 13 May 2026 19:20:03 +0000 Last State: Terminated Reason: Error Message: llerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0513 19:14:46.531634 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0513 19:14:46.531687 1 controller.go:239] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0513 19:14:46.531705 1 controller.go:239] "Starting Controller" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0513 19:14:46.531721 1 controller.go:248] "Starting workers" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0513 19:14:46.531714 1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 E0513 19:18:53.438990 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 E0513 19:19:38.497153 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 E0513 19:19:43.497904 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 I0513 19:19:43.497957 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0513 19:19:43.498078 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 13 May 2026 19:14:20 +0000 Finished: Wed, 13 May 2026 19:19:43 +0000 Ready: True Restart Count: 1 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-lft97 (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-s5vpx (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-s5vpx: 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-lft97 to instance Warning Unhealthy 30m (x2 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.251:9440/healthz": dial tcp 10.0.0.251:9440: connect: connection refused Warning Unhealthy 30m (x2 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.251:9440/readyz": dial tcp 10.0.0.251:9440: connect: connection refused Normal Pulled 30m (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 29m (x2 over 35m) kubelet Created container manager Normal Started 29m (x2 over 35m) kubelet Started container manager