Name: capi-controller-manager-bc4cf8c95-l95n2 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.210 Start Time: Tue, 21 Apr 2026 18:27:45 +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.67 IPs: IP: 10.0.0.67 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://c31ffb80acc42092790b424fffa527df479594b46c23fd85b72c9e130886dfdb 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, 21 Apr 2026 18:37:55 +0000 Last State: Terminated Reason: Error Message: ster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0421 18:28:05.998897 1 controller.go:248] "Starting workers" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0421 18:28:05.999017 1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0421 18:28:05.999085 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 E0421 18:33:10.223024 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 E0421 18:35:12.989737 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 E0421 18:37:16.717033 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 E0421 18:37:21.717172 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 I0421 18:37:21.717229 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0421 18:37:21.717354 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 21 Apr 2026 18:27:46 +0000 Finished: Tue, 21 Apr 2026 18:37:21 +0000 Ready: True Restart Count: 1 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-l95n2 (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-8fnnd (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-8fnnd: 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 11m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-l95n2 to instance Warning Unhealthy 79s (x3 over 99s) kubelet Liveness probe failed: Get "http://10.0.0.67:9440/healthz": dial tcp 10.0.0.67:9440: connect: connection refused Normal Killing 79s kubelet Container manager failed liveness probe, will be restarted Normal Pulled 69s (x2 over 11m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 69s (x2 over 11m) kubelet Created container manager Normal Started 69s (x2 over 11m) kubelet Started container manager Warning Unhealthy 69s (x5 over 99s) kubelet Readiness probe failed: Get "http://10.0.0.67:9440/readyz": dial tcp 10.0.0.67:9440: connect: connection refused