Name: capi-controller-manager-bc4cf8c95-s4jkb Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.169 Start Time: Wed, 25 Feb 2026 20:18:29 +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.154 IPs: IP: 10.0.0.154 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://398269f9e46d185b3af69183bad8de228dc6cf05726e05d81e6a146c244c11c0 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, 25 Feb 2026 20:25:03 +0000 Last State: Terminated Reason: Error Message: ter.x-k8s.io" controllerKind="MachineDeployment" I0225 20:23:59.649452 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0225 20:23:59.649504 1 controller.go:239] "Starting Controller" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0225 20:23:59.649515 1 controller.go:248] "Starting workers" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" worker count=10 I0225 20:23:59.649576 1 controller.go:239] "Starting Controller" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0225 20:23:59.649587 1 controller.go:248] "Starting workers" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0225 20:23:59.649963 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0225 20:23:59.649979 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 E0225 20:24:04.540846 1 leaderelection.go:429] Failed to update lock optimistically: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path E0225 20:24:09.540939 1 leaderelection.go:472] Failed to update lock: Put "https://10.96.0.1:443/apis/coordination.k8s.io/v1/namespaces/capi-system/leases/controller-leader-election-capi?timeout=5s": context deadline exceeded I0225 20:24:09.541003 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0225 20:24:09.541049 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 25 Feb 2026 20:23:34 +0000 Finished: Wed, 25 Feb 2026 20:24:36 +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-s4jkb (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-wb48f (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-wb48f: 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 34m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-s4jkb to instance Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.154:9440/healthz": dial tcp 10.0.0.154:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 29m (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 29m (x11 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.154:9440/readyz": dial tcp 10.0.0.154:9440: connect: connection refused Normal Created 29m (x2 over 34m) kubelet Created container manager Normal Started 29m (x2 over 34m) kubelet Started container manager Warning Unhealthy 28m (x2 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.154:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 28m (x3 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.154:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)