Name: capi-controller-manager-67b46dd44f-pghf5 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/162.253.55.227 Start Time: Thu, 19 Feb 2026 06:09:35 +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.60 IPs: IP: 172.24.0.60 Controlled By: ReplicaSet/capi-controller-manager-67b46dd44f Containers: manager: Container ID: containerd://e2a76a446e2ad99c110dddb29aba4eb0e28d6d3dbdc185f69b2640e81cf00ba0 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 06:14:50 +0000 Last State: Terminated Reason: Error Message: nd="ClusterResourceSet" I0219 06:10:06.404856 1 controller.go:248] "Starting workers" controller="topology/machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=1 I0219 06:10:06.404867 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0219 06:13:41.418757 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 E0219 06:14:16.146497 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 E0219 06:14:21.146971 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": net/http: request canceled (Client.Timeout exceeded while awaiting headers) I0219 06:14:21.147032 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded I0219 06:14:21.147292 1 recorder.go:104] "capi-controller-manager-67b46dd44f-pghf5_0e6798cf-b049-4b97-9a0c-10424b478fd8 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"31c56dc8-b0ee-4735-9dc6-28be5e965dba","apiVersion":"coordination.k8s.io/v1","resourceVersion":"24630"} reason="LeaderElection" E0219 06:14:21.147304 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 19 Feb 2026 06:09:36 +0000 Finished: Thu, 19 Feb 2026 06:14:21 +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-67b46dd44f-pghf5 (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-qpc2n (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-qpc2n: 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 23m default-scheduler Successfully assigned capi-system/capi-controller-manager-67b46dd44f-pghf5 to instance Normal Pulled 18m (x2 over 23m) kubelet Container image "registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 18m (x3 over 18m) kubelet Liveness probe failed: Get "http://172.24.0.60:9440/healthz": dial tcp 172.24.0.60:9440: connect: connection refused Warning Unhealthy 18m (x4 over 18m) kubelet Readiness probe failed: Get "http://172.24.0.60:9440/readyz": dial tcp 172.24.0.60:9440: connect: connection refused Normal Killing 18m kubelet Container manager failed liveness probe, will be restarted Normal Created 18m (x2 over 23m) kubelet Created container manager Normal Started 18m (x2 over 23m) kubelet Started container manager