Name: capi-controller-manager-bc4cf8c95-ksn2z Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.238 Start Time: Fri, 29 May 2026 22:44: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.94 IPs: IP: 10.0.0.94 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://1ffa4fce79719cf99513b1bac09e1cc006af70ae91b728d6a58520ed111e16b9 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: Fri, 29 May 2026 22:52:18 +0000 Last State: Terminated Reason: Error Message: W0529 22:51:57.782725 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0529 22:51:57.783080 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0529 22:51:57.783103 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0529 22:51:57.783108 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0529 22:51:57.783112 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false E0529 22:51:57.783656 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: Fri, 29 May 2026 22:51:57 +0000 Finished: Fri, 29 May 2026 22:51:57 +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-ksn2z (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-g2fjx (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-g2fjx: 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 38m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-ksn2z to instance Warning Unhealthy 34m kubelet Readiness probe failed: Get "http://10.0.0.94:9440/readyz": dial tcp 10.0.0.94:9440: connect: connection refused Warning Unhealthy 34m kubelet Liveness probe failed: Get "http://10.0.0.94:9440/healthz": dial tcp 10.0.0.94:9440: connect: connection refused Normal Pulled 34m (x2 over 38m) 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 38m) kubelet Created container manager Normal Started 34m (x2 over 38m) kubelet Started container manager Warning Unhealthy 32m (x3 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.94:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Normal Killing 32m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 31m (x13 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.94:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 30m kubelet Readiness probe failed: Get "http://10.0.0.94:9440/readyz": read tcp 10.0.0.11:51428->10.0.0.94:9440: read: connection reset by peer