Name: capi-controller-manager-bc4cf8c95-82nmr Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.242 Start Time: Mon, 11 May 2026 06:27: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.112 IPs: IP: 10.0.0.112 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://3925c3d0dc76db6ba321bdd513603a2cad07ca8c826cad20655b9cf8b79b2a8a 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: Mon, 11 May 2026 06:37:31 +0000 Last State: Terminated Reason: Error Message: W0511 06:35:34.839329 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0511 06:35:34.839683 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0511 06:35:34.839704 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0511 06:35:34.839709 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0511 06:35:34.839713 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false Exit Code: 2 Started: Mon, 11 May 2026 06:35:34 +0000 Finished: Mon, 11 May 2026 06:36:03 +0000 Ready: True Restart Count: 5 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-82nmr (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-rwhkj (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-rwhkj: 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 44m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-82nmr to instance Warning Unhealthy 38m (x3 over 39m) kubelet Liveness probe failed: Get "http://10.0.0.112:9440/healthz": dial tcp 10.0.0.112:9440: connect: connection refused Normal Killing 38m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 37m (x3 over 44m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 37m (x3 over 44m) kubelet Created container manager Normal Started 37m (x3 over 44m) kubelet Started container manager Warning Unhealthy 37m (x13 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.112:9440/readyz": dial tcp 10.0.0.112:9440: connect: connection refused Warning BackOff 34m (x7 over 35m) kubelet Back-off restarting failed container manager in pod capi-controller-manager-bc4cf8c95-82nmr_capi-system(5b5695bc-a284-4836-8780-ba9312a1ba69)