Name: capi-controller-manager-bc4cf8c95-hzgtd Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.19.214.127 Start Time: Tue, 12 May 2026 02:54:18 +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.235 IPs: IP: 10.0.0.235 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://02cedc937e4d8576402bcc2b573e15768a556de9bbfd7d8da2c366fdc2d04b0a 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, 12 May 2026 03:01:53 +0000 Last State: Terminated Reason: Error Message: W0512 03:01:34.839650 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0512 03:01:34.840053 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0512 03:01:34.840079 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0512 03:01:34.840085 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0512 03:01:34.840090 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false E0512 03:01:34.840616 1 main.go:346] "Unable to start manager" err="failed to get the Kubernetes version: Get \"https://10.96.0.1:443/version?timeout=32s\": dial tcp 10.96.0.1:443: connect: connection refused" logger="setup" Exit Code: 1 Started: Tue, 12 May 2026 03:01:34 +0000 Finished: Tue, 12 May 2026 03:01:34 +0000 Ready: True Restart Count: 3 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-hzgtd (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-htt5z (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-htt5z: 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 40m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-hzgtd to instance Normal Killing 36m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 35m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 34m (x2 over 40m) kubelet Created container manager Normal Started 34m (x2 over 40m) kubelet Started container manager Warning Unhealthy 34m (x14 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.235:9440/readyz": dial tcp 10.0.0.235:9440: connect: connection refused Warning Unhealthy 34m (x5 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.235:9440/healthz": dial tcp 10.0.0.235:9440: connect: connection refused