Name: capi-controller-manager-bc4cf8c95-pkqkp Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.222 Start Time: Tue, 14 Apr 2026 06:41:17 +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.61 IPs: IP: 10.0.0.61 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://4439aa66b072c8db87c9ff493629228096401b761d0b83b95cfc0b7a3a4b51a8 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, 14 Apr 2026 06:47:12 +0000 Last State: Terminated Reason: Error Message: inepool" controllerGroup="cluster.x-k8s.io" controllerKind="MachinePool" worker count=10 I0414 06:46:17.457086 1 controller.go:239] "Starting Controller" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0414 06:46:17.457101 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0414 06:46:17.457192 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0414 06:46:17.457207 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0414 06:46:17.467860 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0414 06:46:17.467885 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0414 06:46:22.340302 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 E0414 06:46:27.339899 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 I0414 06:46:27.339947 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0414 06:46:27.340003 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 14 Apr 2026 06:45:54 +0000 Finished: Tue, 14 Apr 2026 06:46: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-pkqkp (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-xjnr5 (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-xjnr5: 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 35m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-pkqkp to instance Normal Created 30m (x2 over 35m) kubelet Created container manager Normal Started 30m (x2 over 35m) kubelet Started container manager Warning Unhealthy 30m (x6 over 31m) kubelet Liveness probe failed: Get "http://10.0.0.61:9440/healthz": dial tcp 10.0.0.61:9440: connect: connection refused Normal Killing 30m (x2 over 31m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 29m (x11 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.61:9440/readyz": dial tcp 10.0.0.61:9440: connect: connection refused Normal Pulled 29m (x3 over 35m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine