Name: capi-controller-manager-bc4cf8c95-tjnwq Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.72 Start Time: Thu, 23 Apr 2026 08:36:43 +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.169 IPs: IP: 10.0.0.169 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://2fcaa4f0867cf740a291456f14df1d774a67a958d5bd763a7540692cf7d7e7b6 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, 23 Apr 2026 08:42:43 +0000 Last State: Terminated Reason: Error Message: ontroller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0423 08:41:26.364919 1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0423 08:41:26.364933 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0423 08:41:26.364926 1 controller.go:239] "Starting Controller" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0423 08:41:26.364962 1 controller.go:248] "Starting workers" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0423 08:41:26.364934 1 controller.go:239] "Starting Controller" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0423 08:41:26.365039 1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 E0423 08:41:42.150566 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 E0423 08:41:47.151480 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) I0423 08:41:47.151542 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0423 08:41:47.151631 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 23 Apr 2026 08:41:04 +0000 Finished: Thu, 23 Apr 2026 08:41:47 +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-tjnwq (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-gnstt (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-gnstt: 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-tjnwq to instance Normal Pulled 41m (x2 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 41m (x2 over 45m) kubelet Created container manager Normal Started 41m (x2 over 45m) kubelet Started container manager Warning Unhealthy 40m (x12 over 42m) kubelet Readiness probe failed: Get "http://10.0.0.169:9440/readyz": dial tcp 10.0.0.169:9440: connect: connection refused Warning Unhealthy 40m (x6 over 42m) kubelet Liveness probe failed: Get "http://10.0.0.169:9440/healthz": dial tcp 10.0.0.169:9440: connect: connection refused Normal Killing 40m (x2 over 41m) kubelet Container manager failed liveness probe, will be restarted