Name: capi-controller-manager-bc4cf8c95-wqpdz Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.156 Start Time: Thu, 14 May 2026 06:15:45 +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.111 IPs: IP: 10.0.0.111 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://7c43b30090fbe5b7b749908896e09eace9edcde11f2eabe50d9d89f9c10400e3 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, 14 May 2026 06:23:45 +0000 Last State: Terminated Reason: Error Message: ng workers" controller="clusterresourceset" controllerGroup="addons.cluster.x-k8s.io" controllerKind="ClusterResourceSet" worker count=10 I0514 06:21:14.486579 1 controller.go:239] "Starting Controller" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" I0514 06:21:14.486593 1 controller.go:248] "Starting workers" controller="machinehealthcheck" controllerGroup="cluster.x-k8s.io" controllerKind="MachineHealthCheck" worker count=10 I0514 06:21:14.486613 1 controller.go:239] "Starting Controller" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" I0514 06:21:14.486622 1 controller.go:248] "Starting workers" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" worker count=10 I0514 06:21:14.486666 1 controller.go:239] "Starting Controller" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" I0514 06:21:14.486680 1 controller.go:248] "Starting workers" controller="crdmigrator" controllerGroup="apiextensions.k8s.io" controllerKind="CustomResourceDefinition" worker count=1 E0514 06:21:21.393473 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 E0514 06:21:26.393209 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 I0514 06:21:26.393444 1 leaderelection.go:297] failed to renew lease capi-system/controller-leader-election-capi: context deadline exceeded E0514 06:21:26.393828 1 main.go:433] "Problem running manager" err="leader election lost" logger="setup" Exit Code: 1 Started: Thu, 14 May 2026 06:20:42 +0000 Finished: Thu, 14 May 2026 06:21:26 +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-wqpdz (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-njc4x (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-njc4x: 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 41m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-wqpdz to instance Normal Pulled 36m (x2 over 41m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 36m (x2 over 41m) kubelet Created container manager Normal Started 36m (x2 over 41m) kubelet Started container manager Warning Unhealthy 35m (x6 over 37m) kubelet Liveness probe failed: Get "http://10.0.0.111:9440/healthz": dial tcp 10.0.0.111:9440: connect: connection refused Normal Killing 35m (x2 over 36m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x12 over 37m) kubelet Readiness probe failed: Get "http://10.0.0.111:9440/readyz": dial tcp 10.0.0.111:9440: connect: connection refused