Name: capi-kubeadm-control-plane-controller-manager-bdfc6fdd8-zsj4k Namespace: capi-kubeadm-control-plane-system Priority: 0 Service Account: capi-kubeadm-control-plane-manager Node: instance/199.204.45.70 Start Time: Thu, 23 Apr 2026 01:06:54 +0000 Labels: cluster.x-k8s.io/provider=control-plane-kubeadm control-plane=controller-manager pod-template-hash=bdfc6fdd8 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.114 IPs: IP: 10.0.0.114 Controlled By: ReplicaSet/capi-kubeadm-control-plane-controller-manager-bdfc6fdd8 Containers: manager: Container ID: containerd://439d1dc5bbd4dd42b0c5fa04251c98a1883192f6bbc1c36da129f49ee136888d Image: harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.10.5 Image ID: harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-control-plane-controller@sha256:a780eabc911316b348f06fb02c43773b311a239b72496c24b47281ba1af456ba 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,ClusterTopology=true,KubeadmBootstrapFormatIgnition=false,PriorityQueue=false State: Running Started: Thu, 23 Apr 2026 01:13:35 +0000 Last State: Terminated Reason: Error Message: I0423 01:13:33.159194 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0423 01:13:33.159360 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0423 01:13:33.159378 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0423 01:13:33.159393 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false E0423 01:13:33.161355 1 main.go:319] "unable to start manager" err="failed to determine if *v1.Secret is namespaced: failed to get restmapping: failed to get server groups: Get \"https://10.96.0.1:443/api\": dial tcp 10.96.0.1:443: connect: connection refused" logger="setup" Exit Code: 1 Started: Thu, 23 Apr 2026 01:13:33 +0000 Finished: Thu, 23 Apr 2026 01:13:33 +0000 Ready: True Restart Count: 2 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-kubeadm-control-plane-system (v1:metadata.namespace) POD_NAME: capi-kubeadm-control-plane-controller-manager-bdfc6fdd8-zsj4k (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-2kdvl (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capi-kubeadm-control-plane-webhook-service-cert Optional: false kube-api-access-2kdvl: 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 33m default-scheduler Successfully assigned capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-bdfc6fdd8-zsj4k to instance Warning Unhealthy 27m (x3 over 28m) kubelet Liveness probe failed: Get "http://10.0.0.114:9440/healthz": dial tcp 10.0.0.114:9440: connect: connection refused Normal Killing 27m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 27m (x3 over 33m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.10.5" already present on machine Normal Created 27m (x3 over 33m) kubelet Created container manager Normal Started 27m (x3 over 33m) kubelet Started container manager Warning Unhealthy 27m (x9 over 28m) kubelet Readiness probe failed: Get "http://10.0.0.114:9440/readyz": dial tcp 10.0.0.114:9440: connect: connection refused