Name: capi-controller-manager-bc4cf8c95-m2wgt Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.242 Start Time: Tue, 19 May 2026 17:06:36 +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.167 IPs: IP: 10.0.0.167 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://e58783b741d132a3a91bda9791e5bda9e45f58098de137258935585bd99897d5 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: Tue, 19 May 2026 17:31:47 +0000 Last State: Terminated Reason: Error Message: .cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0519 17:31:03.708980 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0519 17:31:03.709004 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 I0519 17:31:03.709248 1 controller.go:239] "Starting Controller" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" I0519 17:31:03.709274 1 controller.go:248] "Starting workers" controller="machinepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" worker count=10 E0519 17:31:29.224605 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 E0519 17:31:34.223460 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 I0519 17:31:34.223515 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0519 17:31:34.223639 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" I0519 17:31:34.223654 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-m2wgt_fcb96137-b0ec-49a0-bd4f-f101056352bf stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"8faa40a3-40b9-4ee0-8f62-ae72e41e2cca","apiVersion":"coordination.k8s.io/v1","resourceVersion":"45262"} reason="LeaderElection" Exit Code: 1 Started: Tue, 19 May 2026 17:30:42 +0000 Finished: Tue, 19 May 2026 17:31:34 +0000 Ready: True Restart Count: 4 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-m2wgt (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-bcq5j (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-bcq5j: 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 32m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-m2wgt to instance Normal Killing 28m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 25m (x18 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.167:9440/readyz": dial tcp 10.0.0.167:9440: connect: connection refused Normal Pulled 8m7s (x5 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 7m58s (x3 over 32m) kubelet Created container manager Normal Started 7m58s (x3 over 32m) kubelet Started container manager Warning Unhealthy 7m4s (x4 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.167:9440/healthz": dial tcp 10.0.0.167:9440: connect: connection refused