Name: capi-controller-manager-bc4cf8c95-2lvkx Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.95 Start Time: Tue, 19 May 2026 05:53:01 +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.1 IPs: IP: 10.0.0.1 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://28c8d9802c4618a09564a08426a2c7228c641c0411bbfa09711bd81f4d9e2985 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, 19 May 2026 05:56:58 +0000 Last State: Terminated Reason: Error Message: hineSet" I0519 05:53:23.795214 1 controller.go:248] "Starting workers" controller="topology/machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=1 I0519 05:53:23.795434 1 controller.go:239] "Starting Controller" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0519 05:53:23.795462 1 controller.go:248] "Starting workers" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0519 05:53:23.795879 1 controller.go:239] "Starting Controller" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" I0519 05:53:23.795896 1 controller.go:248] "Starting workers" controller="clusterclass" controllerGroup="cluster.x-k8s.io" controllerKind="ClusterClass" worker count=10 I0519 05:53:23.796073 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0519 05:53:23.796102 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0519 05:56:24.720803 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 E0519 05:56:29.721390 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 I0519 05:56:29.722549 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0519 05:56:29.722629 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Tue, 19 May 2026 05:53:02 +0000 Finished: Tue, 19 May 2026 05:56:29 +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-2lvkx (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-hn896 (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-hn896: 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-2lvkx to instance Warning Unhealthy 30m (x4 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.1:9440/readyz": dial tcp 10.0.0.1:9440: connect: connection refused Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.1:9440/healthz": dial tcp 10.0.0.1:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted 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 Normal Created 30m (x2 over 34m) kubelet Created container manager Normal Started 30m (x2 over 34m) kubelet Started container manager