Name: capi-controller-manager-bc4cf8c95-v8z9g Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.19.213.140 Start Time: Tue, 05 May 2026 17:51:06 +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.118 IPs: IP: 10.0.0.118 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://23e60ce38c064f7ea96e76e56c92d2a6b2d6f498286e0f0013212d718e520ccd 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 18:00:12 +0000 Last State: Terminated Reason: Error Message: W0505 17:59:40.465214 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0505 17:59:40.465586 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0505 17:59:40.465603 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0505 17:59:40.465609 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0505 17:59:40.465614 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false E0505 17:59:40.466450 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, 05 May 2026 17:59:40 +0000 Finished: Tue, 05 May 2026 17:59:40 +0000 Ready: True Restart Count: 4 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-v8z9g (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-mhgl9 (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-mhgl9: 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-v8z9g to instance Warning Unhealthy 35m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.118:9440/healthz": dial tcp 10.0.0.118:9440: connect: connection refused Warning Unhealthy 34m (x8 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.118:9440/readyz": dial tcp 10.0.0.118:9440: connect: connection refused Normal Pulled 34m (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 34m (x2 over 40m) kubelet Created container manager Normal Started 34m (x2 over 40m) kubelet Started container manager Normal Killing 33m (x2 over 35m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 33m (x3 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.118:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x4 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.118:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)