Name: capi-controller-manager-bc4cf8c95-5wxlv Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.229 Start Time: Wed, 10 Jun 2026 09:21:26 +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.245 IPs: IP: 10.0.0.245 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://2c3338851ae202260ebfc761083d142fa36b26eb91b62dcb4cfec0b084c380ba 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, 10 Jun 2026 09:28:49 +0000 Last State: Terminated Reason: Error Message: Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0610 09:26:33.270222 1 controller.go:239] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0610 09:26:33.271316 1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 I0610 09:26:33.272455 1 controller.go:239] "Starting Controller" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" I0610 09:26:33.272481 1 controller.go:248] "Starting workers" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=10 I0610 09:26:33.272651 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0610 09:26:33.272712 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 E0610 09:26:50.294767 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 E0610 09:26:55.293587 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 I0610 09:26:55.293728 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0610 09:26:55.293841 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Wed, 10 Jun 2026 09:26:12 +0000 Finished: Wed, 10 Jun 2026 09:27:27 +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-5wxlv (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-cr5w2 (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-cr5w2: 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 39m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-5wxlv to instance Normal Started 38m kubelet Started container manager Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.245:9440/healthz": dial tcp 10.0.0.245:9440: connect: connection refused Normal Pulled 34m (x2 over 38m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 34m (x12 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.245:9440/readyz": dial tcp 10.0.0.245:9440: connect: connection refused Normal Killing 34m (x5 over 35m) kubelet Container manager failed liveness probe, will be restarted Normal Created 34m (x2 over 38m) kubelet Created container manager Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.245:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)