Name: capi-controller-manager-bc4cf8c95-tf26r Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.19.213.238 Start Time: Tue, 12 May 2026 06:51:20 +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.127 IPs: IP: 10.0.0.127 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://bb15beda73756a2d1daf771198d9bdc81e5590ea2dccbf8b2325d302c6c05111 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 07:01:32 +0000 Last State: Terminated Reason: Error Message: W0512 07:01:19.235496 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0512 07:01:19.235811 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0512 07:01:19.235829 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0512 07:01:19.235833 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0512 07:01:19.235837 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false E0512 07:01:19.236293 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 07:01:19 +0000 Finished: Tue, 12 May 2026 07:01:19 +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-tf26r (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-8km5z (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-8km5z: 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 42m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-tf26r to instance Warning Unhealthy 37m (x3 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.127:9440/healthz": dial tcp 10.0.0.127:9440: connect: connection refused Warning Unhealthy 37m (x8 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.127:9440/readyz": dial tcp 10.0.0.127:9440: connect: connection refused Normal Pulled 37m (x2 over 42m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 37m (x2 over 42m) kubelet Created container manager Normal Started 37m (x2 over 42m) kubelet Started container manager Normal Killing 34m (x2 over 37m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x3 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.127:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 34m (x5 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.127:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)