Name: capi-controller-manager-67b46dd44f-tsll4 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.222 Start Time: Thu, 19 Feb 2026 19:47:41 +0000 Labels: cluster.x-k8s.io/provider=cluster-api control-plane=controller-manager pod-template-hash=67b46dd44f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 172.24.0.149 IPs: IP: 172.24.0.149 Controlled By: ReplicaSet/capi-controller-manager-67b46dd44f Containers: manager: Container ID: containerd://b552d7eda382afdea1fec38ee9b7aa48b0361d510172e0028ede4451cbf36e57 Image: registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5 Image ID: 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: Thu, 19 Feb 2026 19:54:11 +0000 Last State: Terminated Reason: Error Message: r="clustercache" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0219 19:53:45.771419 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0219 19:53:45.771429 1 controller.go:270] "All workers finished" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0219 19:53:45.771440 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0219 19:53:45.771450 1 controller.go:270] "All workers finished" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0219 19:53:45.771460 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0219 19:53:45.771476 1 controller.go:270] "All workers finished" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0219 19:53:45.771486 1 controller.go:268] "Shutdown signal received, waiting for all workers to finish" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0219 19:53:45.771501 1 controller.go:270] "All workers finished" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0219 19:53:45.771687 1 controller.go:270] "All workers finished" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0219 19:53:45.771726 1 controller.go:270] "All workers finished" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" E0219 19:53:45.770595 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 19 Feb 2026 19:52:24 +0000 Finished: Thu, 19 Feb 2026 19:54:07 +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-67b46dd44f-tsll4 (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-7rbbf (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-7rbbf: 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 28m default-scheduler Successfully assigned capi-system/capi-controller-manager-67b46dd44f-tsll4 to instance Warning Unhealthy 24m (x3 over 24m) kubelet Liveness probe failed: Get "http://172.24.0.149:9440/healthz": dial tcp 172.24.0.149:9440: connect: connection refused Normal Killing 24m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 23m (x8 over 24m) kubelet Readiness probe failed: Get "http://172.24.0.149:9440/readyz": dial tcp 172.24.0.149:9440: connect: connection refused Warning Unhealthy 22m (x2 over 22m) kubelet Liveness probe failed: Get "http://172.24.0.149:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 22m (x2 over 22m) kubelet Readiness probe failed: Get "http://172.24.0.149:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 22m (x3 over 28m) kubelet Container image "registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 21m (x3 over 28m) kubelet Created container manager Normal Started 21m (x3 over 28m) kubelet Started container manager