Name: capi-controller-manager-bc4cf8c95-pmtbr Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.240 Start Time: Thu, 16 Apr 2026 23:22:53 +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.5 IPs: IP: 10.0.0.5 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://40b5795a5db88aa82ba834d86e11f3c88d4ef0184cb459a812706a77e0924ed7 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, 16 Apr 2026 23:30:45 +0000 Last State: Terminated Reason: Error Message: ollerKind="MachineHealthCheck" I0416 23:28:39.839262 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0416 23:28:39.874240 1 controller.go:239] "Starting Controller" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" I0416 23:28:39.874265 1 controller.go:248] "Starting workers" controller="topology/cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" worker count=10 I0416 23:28:39.874316 1 controller.go:239] "Starting Controller" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" I0416 23:28:39.874323 1 controller.go:248] "Starting workers" controller="machinedeployment" controllerGroup="cluster.x-k8s.io" controllerKind="MachineDeployment" worker count=10 I0416 23:28:39.874318 1 controller.go:239] "Starting Controller" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" I0416 23:28:39.874343 1 controller.go:248] "Starting workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 E0416 23:29:14.172684 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 E0416 23:29:19.172870 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 I0416 23:29:19.174237 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0416 23:29:19.174363 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 16 Apr 2026 23:28:20 +0000 Finished: Thu, 16 Apr 2026 23:29:43 +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-pmtbr (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-xkp97 (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-xkp97: 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 20m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-pmtbr to instance Normal Killing 16m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 15m (x11 over 16m) kubelet Readiness probe failed: Get "http://10.0.0.5:9440/readyz": dial tcp 10.0.0.5:9440: connect: connection refused Normal Pulled 15m (x2 over 20m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 15m (x2 over 20m) kubelet Created container manager Normal Started 15m (x2 over 20m) kubelet Started container manager Warning Unhealthy 13m (x2 over 13m) kubelet Liveness probe failed: Get "http://10.0.0.5:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 13m (x2 over 13m) kubelet Readiness probe failed: Get "http://10.0.0.5:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 13m (x4 over 16m) kubelet Liveness probe failed: Get "http://10.0.0.5:9440/healthz": dial tcp 10.0.0.5:9440: connect: connection refused