Name: capi-controller-manager-bc4cf8c95-8g5gq Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.210 Start Time: Thu, 28 May 2026 02:54:49 +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.35 IPs: IP: 10.0.0.35 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://f2c58d7a36bacefac908ff5f0a44f0ef53b812097413553d70c3c9b556a89a09 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, 28 May 2026 02:59:10 +0000 Last State: Terminated Reason: Error Message: 239] "Starting Controller" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0528 02:55:20.636087 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0528 02:55:20.636065 1 controller.go:248] "Starting workers" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=10 I0528 02:55:20.635984 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 I0528 02:55:20.636000 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 I0528 02:55:20.640539 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0528 02:55:20.640557 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0528 02:58:44.309410 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 E0528 02:58:49.309038 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 I0528 02:58:49.309093 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0528 02:58:49.309172 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 28 May 2026 02:54:50 +0000 Finished: Thu, 28 May 2026 02:58:49 +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-8g5gq (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-njnx2 (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-njnx2: 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 32m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-8g5gq to instance Normal Pulled 27m (x2 over 32m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 27m (x2 over 32m) kubelet Created container manager Normal Started 27m (x2 over 32m) kubelet Started container manager Warning Unhealthy 27m (x4 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.35:9440/readyz": dial tcp 10.0.0.35:9440: connect: connection refused Warning Unhealthy 27m (x3 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.35:9440/healthz": dial tcp 10.0.0.35:9440: connect: connection refused Normal Killing 27m kubelet Container manager failed liveness probe, will be restarted