Name: capi-controller-manager-bc4cf8c95-l54cg Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.242 Start Time: Sat, 09 May 2026 13:47:42 +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.94 IPs: IP: 10.0.0.94 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://acc19486071e3b89e965314a3fdce833bdfabf8596fc8a8e66772a3295c5ff5d 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: Sat, 09 May 2026 13:54:25 +0000 Last State: Terminated Reason: Error Message: 1 controller.go:248] "Starting workers" controller="topology/machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=1 I0509 13:53:11.166156 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0509 13:53:11.166185 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 I0509 13:53:11.166300 1 controller.go:239] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0509 13:53:11.166322 1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 I0509 13:53:11.166398 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0509 13:53:11.166412 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0509 13:53:25.137169 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 E0509 13:53:30.136450 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 I0509 13:53:30.136504 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0509 13:53:30.136573 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sat, 09 May 2026 13:52:45 +0000 Finished: Sat, 09 May 2026 13:53: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-l54cg (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-g8d4j (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-g8d4j: 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 33m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-l54cg to instance Normal Pulled 28m (x2 over 33m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 28m (x2 over 33m) kubelet Created container manager Normal Started 28m (x2 over 33m) kubelet Started container manager Warning Unhealthy 27m (x6 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.94:9440/healthz": dial tcp 10.0.0.94:9440: connect: connection refused Normal Killing 27m (x2 over 29m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 27m (x12 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.94:9440/readyz": dial tcp 10.0.0.94:9440: connect: connection refused