Name: capi-controller-manager-bc4cf8c95-5xkvb Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.19.213.219 Start Time: Tue, 05 May 2026 23:07:43 +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.194 IPs: IP: 10.0.0.194 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://b367b4bb87d135933636e957a74ed32a382efcf7a51b1a3f0054bd1042a53423 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, 05 May 2026 23:16:31 +0000 Last State: Terminated Reason: Error Message: W0505 23:15:13.616115 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0505 23:15:13.616468 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0505 23:15:13.616489 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0505 23:15:13.616493 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0505 23:15:13.616497 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false Exit Code: 2 Started: Tue, 05 May 2026 23:15:13 +0000 Finished: Tue, 05 May 2026 23:15:43 +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-5xkvb (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-cdg57 (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-cdg57: 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 35m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-5xkvb to instance Normal Killing 31m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 30m (x2 over 35m) 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 35m) kubelet Created container manager Normal Started 30m (x2 over 35m) kubelet Started container manager Warning Unhealthy 30m (x14 over 31m) kubelet Readiness probe failed: Get "http://10.0.0.194:9440/readyz": dial tcp 10.0.0.194:9440: connect: connection refused Warning Unhealthy 30m (x5 over 31m) kubelet Liveness probe failed: Get "http://10.0.0.194:9440/healthz": dial tcp 10.0.0.194:9440: connect: connection refused