Name: capi-controller-manager-bc4cf8c95-vdgk8 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.77 Start Time: Sun, 10 May 2026 04:51:48 +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.30 IPs: IP: 10.0.0.30 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://75bd2206f63d94a108840ab4190ed350be1f3490b6a709e03dba96bec74bd781 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, 10 May 2026 04:57:19 +0000 Last State: Terminated Reason: Error Message: "Starting workers" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=10 I0510 04:56:27.203364 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0510 04:56:27.203380 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0510 04:56:27.203610 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0510 04:56:27.203626 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 I0510 04:56:27.204826 1 controller.go:239] "Starting Controller" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" I0510 04:56:27.204843 1 controller.go:248] "Starting workers" controller="machineset" controllerGroup="cluster.x-k8s.io" controllerKind="MachineSet" worker count=10 E0510 04:56:50.905978 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 E0510 04:56:55.898626 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 I0510 04:56:55.898912 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0510 04:56:55.899007 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Sun, 10 May 2026 04:56:05 +0000 Finished: Sun, 10 May 2026 04:57:16 +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-vdgk8 (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-jjgvb (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-jjgvb: 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-vdgk8 to instance Warning Unhealthy 30m (x3 over 30m) kubelet Liveness probe failed: Get "http://10.0.0.30:9440/healthz": dial tcp 10.0.0.30:9440: connect: connection refused Normal Killing 30m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 30m (x5 over 30m) kubelet Readiness probe failed: Get "http://10.0.0.30:9440/readyz": dial tcp 10.0.0.30:9440: connect: connection refused Warning Unhealthy 29m (x2 over 29m) kubelet Liveness probe failed: Get "http://10.0.0.30:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 29m (x2 over 29m) kubelet Readiness probe failed: Get "http://10.0.0.30:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Pulled 28m (x3 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 28m (x3 over 34m) kubelet Created container manager Normal Started 28m (x3 over 34m) kubelet Started container manager