Name: capi-controller-manager-bc4cf8c95-s6jgz Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.233 Start Time: Thu, 14 May 2026 17:41:23 +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.20 IPs: IP: 10.0.0.20 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://ac0ce8a77946bdad12cc9fab583e3955b2b2a34a7ceb92f826c949dfbb3de18d 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: Thu, 14 May 2026 18:11:24 +0000 Last State: Terminated Reason: Error Message: binding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0514 17:41:53.816347 1 controller.go:239] "Starting Controller" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0514 17:41:53.816365 1 controller.go:248] "Starting workers" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" worker count=10 I0514 17:41:53.817826 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0514 17:41:53.817875 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0514 18:10:56.337033 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 E0514 18:11:01.335617 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 I0514 18:11:01.335694 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded I0514 18:11:01.336078 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-s6jgz_89f1ae2e-7b26-43b2-b21e-3521ce022c4d stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"cd8a3d2a-777d-4277-b765-6349c4e72d7f","apiVersion":"coordination.k8s.io/v1","resourceVersion":"38968"} reason="LeaderElection" E0514 18:11:01.336835 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 14 May 2026 17:41:24 +0000 Finished: Thu, 14 May 2026 18:11:01 +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-s6jgz (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-d9nfz (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-d9nfz: 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-s6jgz to instance Warning Unhealthy 4m15s (x2 over 4m25s) kubelet Readiness probe failed: Get "http://10.0.0.20:9440/readyz": dial tcp 10.0.0.20:9440: connect: connection refused Warning Unhealthy 4m15s (x2 over 4m25s) kubelet Liveness probe failed: Get "http://10.0.0.20:9440/healthz": dial tcp 10.0.0.20:9440: connect: connection refused Normal Pulled 4m8s (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 4m5s (x2 over 34m) kubelet Created container manager Normal Started 4m5s (x2 over 34m) kubelet Started container manager