Name: capi-controller-manager-bc4cf8c95-dqv4z Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.109 Start Time: Thu, 14 May 2026 06:16:12 +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.11 IPs: IP: 10.0.0.11 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://a82b5704b4468533d8fc2df3ed4f3ef74222ba3382e059b8e962644dd353e58a 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: Thu, 14 May 2026 06:24:14 +0000 Last State: Terminated Reason: Error Message: W0514 06:23:59.341375 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0514 06:23:59.341867 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0514 06:23:59.341895 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0514 06:23:59.341901 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0514 06:23:59.341906 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false E0514 06:24:00.464505 1 main.go:346] "Unable to start manager" err="failed to get the Kubernetes version: unknown" logger="setup" Exit Code: 1 Started: Thu, 14 May 2026 06:23:59 +0000 Finished: Thu, 14 May 2026 06:24:00 +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-dqv4z (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-87gwd (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-87gwd: 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 39m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-dqv4z to instance Normal Created 39m kubelet Created container manager Normal Started 39m kubelet Started container manager Warning Unhealthy 35m (x2 over 35m) kubelet Liveness probe failed: Get "http://10.0.0.11:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 35m (x2 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.11:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 35m kubelet Liveness probe failed: Get "http://10.0.0.11:9440/healthz": dial tcp 10.0.0.11:9440: connect: connection refused Normal Killing 35m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 33m (x2 over 39m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Warning Unhealthy 32m (x16 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.11:9440/readyz": dial tcp 10.0.0.11:9440: connect: connection refused