Name: capi-controller-manager-bc4cf8c95-bmn4v Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.162 Start Time: Thu, 02 Apr 2026 09:50: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.145 IPs: IP: 10.0.0.145 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://b85f492d7fdc656eafc5efeae14ee6cdbf1db87bdd637317625bf76d3c2740ea 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, 02 Apr 2026 09:56:11 +0000 Last State: Terminated Reason: Error Message: " controllerKind="Cluster" worker count=10 I0402 09:55:14.608002 1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0402 09:55:14.608035 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0402 09:55:14.608142 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0402 09:55:14.608151 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0402 09:55:14.608231 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0402 09:55:14.608251 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0402 09:55:28.479848 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 E0402 09:55:33.479906 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 I0402 09:55:33.479990 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0402 09:55:33.480098 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 02 Apr 2026 09:54:56 +0000 Finished: Thu, 02 Apr 2026 09:55:55 +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-bmn4v (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-f42wk (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-f42wk: 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 38m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-bmn4v to instance Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.145:9440/healthz": dial tcp 10.0.0.145:9440: connect: connection refused Normal Created 34m (x2 over 38m) kubelet Created container manager Normal Started 34m (x2 over 38m) kubelet Started container manager Warning Unhealthy 33m (x2 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.145:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x2 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.145:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 33m (x2 over 35m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.145:9440/healthz": read tcp 10.0.0.19:40220->10.0.0.145:9440: read: connection reset by peer Warning Unhealthy 33m kubelet Readiness probe failed: Get "http://10.0.0.145:9440/readyz": read tcp 10.0.0.19:40206->10.0.0.145:9440: read: connection reset by peer Warning Unhealthy 33m (x8 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.145:9440/readyz": dial tcp 10.0.0.145:9440: connect: connection refused Normal Pulled 33m (x3 over 38m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine