Name: capi-controller-manager-bc4cf8c95-vnscq Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.116 Start Time: Fri, 24 Apr 2026 02:16: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.91 IPs: IP: 10.0.0.91 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://899c3c687238fda729127ad42641a67d98bb33139253548c1cfbfc053220f8d8 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 02:21:46 +0000 Last State: Terminated Reason: Error Message: workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0424 02:16:35.467373 1 controller.go:239] "Starting Controller" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" I0424 02:16:35.467395 1 controller.go:248] "Starting workers" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" worker count=10 I0424 02:16:35.468504 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0424 02:16:35.468530 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 I0424 02:16:35.469777 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0424 02:16:35.469804 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 E0424 02:20:58.716942 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 02:21:03.715301 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 02:21:03.715399 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0424 02:21:03.715519 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Fri, 24 Apr 2026 02:16:06 +0000 Finished: Fri, 24 Apr 2026 02:21:12 +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-vnscq (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-c22hd (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-c22hd: 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-vnscq to instance Warning Unhealthy 22m kubelet Readiness probe failed: Get "http://10.0.0.91:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 22m kubelet Liveness probe failed: Get "http://10.0.0.91:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 21m (x2 over 22m) kubelet Liveness probe failed: Get "http://10.0.0.91:9440/healthz": dial tcp 10.0.0.91:9440: connect: connection refused Normal Killing 21m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 21m (x2 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 21m (x2 over 27m) kubelet Created container manager Normal Started 21m (x2 over 27m) kubelet Started container manager Warning Unhealthy 21m (x5 over 22m) kubelet Readiness probe failed: Get "http://10.0.0.91:9440/readyz": dial tcp 10.0.0.91:9440: connect: connection refused