Name:             capi-controller-manager-bc4cf8c95-m6vtx
Namespace:        capi-system
Priority:         0
Service Account:  capi-manager
Node:             instance/162.253.55.221
Start Time:       Tue, 31 Mar 2026 05:48:10 +0000
Labels:           cluster.x-k8s.io/provider=cluster-api
                  control-plane=controller-manager
                  pod-template-hash=bc4cf8c95
Annotations:      <none>
Status:           Running
SeccompProfile:   RuntimeDefault
IP:               10.0.0.95
IPs:
  IP:           10.0.0.95
Controlled By:  ReplicaSet/capi-controller-manager-bc4cf8c95
Containers:
  manager:
    Container ID:  containerd://0865e6e67437c58df63a1e08a074e18bc5f21ba2ab8ffcc45cde15983f39caf6
    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, 31 Mar 2026 05:55:54 +0000
    Last State:  Terminated
      Reason:    Error
      Message:   W0331 05:55:38.343651       1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release.
I0331 05:55:38.344158       1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false
I0331 05:55:38.344187       1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false
I0331 05:55:38.344191       1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false
I0331 05:55:38.344195       1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false
E0331 05:55:38.348203       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, 31 Mar 2026 05:55:38 +0000
      Finished:     Tue, 31 Mar 2026 05:55:38 +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-m6vtx (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-hbdjk (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-hbdjk:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    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  8m29s                   default-scheduler  Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-m6vtx to instance
  Normal   Killing    4m19s                   kubelet            Container manager failed liveness probe, will be restarted
  Normal   Pulled     3m27s (x2 over 8m29s)   kubelet            Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine
  Normal   Created    3m25s (x2 over 8m28s)   kubelet            Created container manager
  Normal   Started    3m25s (x2 over 8m28s)   kubelet            Started container manager
  Warning  Unhealthy  2m29s (x13 over 4m39s)  kubelet            Readiness probe failed: Get "http://10.0.0.95:9440/readyz": dial tcp 10.0.0.95:9440: connect: connection refused
  Warning  Unhealthy  2m29s (x6 over 4m39s)   kubelet            Liveness probe failed: Get "http://10.0.0.95:9440/healthz": dial tcp 10.0.0.95:9440: connect: connection refused