Name: capi-controller-manager-bc4cf8c95-xd75q Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.109 Start Time: Tue, 26 May 2026 06:40:07 +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.217 IPs: IP: 10.0.0.217 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://0de6a96d9f5401d303c1aa6104c008fee1c6f5d193add29d6b030a721b3842b7 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, 26 May 2026 06:46:37 +0000 Last State: Terminated Reason: Error Message: ing Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0526 06:45:04.458244 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0526 06:45:04.458259 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0526 06:45:04.458292 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0526 06:45:04.458306 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0526 06:45:32.700509 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": context deadline exceeded, falling back to slow path E0526 06:45:37.701077 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 I0526 06:45:37.701152 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded I0526 06:45:37.701323 1 recorder.go:104] "capi-controller-manager-bc4cf8c95-xd75q_67886fed-d076-4d96-b372-b5d234ec1302 stopped leading" logger="events" type="Normal" object={"kind":"Lease","namespace":"capi-system","name":"controller-leader-election-capi","uid":"2442360b-d82d-4fc7-91a5-1a09163040de","apiVersion":"coordination.k8s.io/v1","resourceVersion":"25753"} reason="LeaderElection" E0526 06:45:37.701660 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 26 May 2026 06:44:08 +0000 Finished: Tue, 26 May 2026 06:46:31 +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-xd75q (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-xxjcm (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-xxjcm: 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 45m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-xd75q to instance Warning Unhealthy 41m kubelet Liveness probe failed: Get "http://10.0.0.217:9440/healthz": dial tcp 10.0.0.217:9440: connect: connection refused Warning Unhealthy 41m kubelet Readiness probe failed: Get "http://10.0.0.217:9440/readyz": dial tcp 10.0.0.217:9440: connect: connection refused Warning Unhealthy 39m (x3 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.217:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 39m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 38m (x7 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.217:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 38m (x3 over 45m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 38m (x3 over 45m) kubelet Created container manager Normal Started 38m (x3 over 45m) kubelet Started container manager