Name: capi-controller-manager-bc4cf8c95-8f6dv Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.227 Start Time: Sun, 31 May 2026 18:07:02 +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.31 IPs: IP: 10.0.0.31 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://2d2382d73a36517bdc669d7a2c7c9d7e0faee6c83737d9fc06aa20a2b55a5da2 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: Sun, 31 May 2026 18:11:25 +0000 Last State: Terminated Reason: Error Message: chineDeployment" I0531 18:07:30.453094 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0531 18:07:30.453203 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0531 18:07:30.453215 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 I0531 18:07:30.453217 1 controller.go:239] "Starting Controller" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0531 18:07:30.453238 1 controller.go:248] "Starting workers" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" worker count=10 I0531 18:07:30.453257 1 controller.go:239] "Starting Controller" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" I0531 18:07:30.453266 1 controller.go:248] "Starting workers" controller="clusterresourcesetbinding" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSetBinding" worker count=10 E0531 18:10:44.078630 1 leaderelection.go:429] Failed to update lock optimistically: the server was unable to return a response in the time allotted, but may still be processing the request (put leases.coordination.k8s.io controller-leader-election-capi), falling back to slow path E0531 18:10:49.077141 1 leaderelection.go:472] Failed to update lock: 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 I0531 18:10:49.077216 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0531 18:10:49.077287 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sun, 31 May 2026 18:07:03 +0000 Finished: Sun, 31 May 2026 18:10: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-8f6dv (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-fd5v9 (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-fd5v9: 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 34m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-8f6dv to instance Normal Pulled 30m (x2 over 34m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.31:9440/healthz": dial tcp 10.0.0.31:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 29m (x5 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.31:9440/readyz": dial tcp 10.0.0.31:9440: connect: connection refused Normal Created 29m (x2 over 34m) kubelet Created container manager Normal Started 29m (x2 over 34m) kubelet Started container manager