Name: capi-controller-manager-bc4cf8c95-mgnlr Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.19.213.157 Start Time: Thu, 21 May 2026 20:30:30 +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.148 IPs: IP: 10.0.0.148 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://4360732c72b37bae0f391cd2cf774423a78a24617ec1104d916bb9bd5dd484f6 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, 21 May 2026 20:38:44 +0000 Last State: Terminated Reason: StartError Message: failed to create containerd task: failed to create shim task: context canceled Exit Code: 128 Started: Thu, 01 Jan 1970 00:00:00 +0000 Finished: Thu, 21 May 2026 20:38:32 +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-system (v1:metadata.namespace) POD_NAME: capi-controller-manager-bc4cf8c95-mgnlr (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-mh59p (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-mh59p: 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 41m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-mgnlr to instance Normal Started 41m kubelet Started container manager Warning Unhealthy 37m (x3 over 37m) kubelet Liveness probe failed: Get "http://10.0.0.148:9440/healthz": dial tcp 10.0.0.148:9440: connect: connection refused Normal Killing 37m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 36m (x2 over 41m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/cluster-api/cluster-api-controller:v1.10.5" already present on machine Normal Created 35m (x2 over 41m) kubelet Created container manager Warning Unhealthy 34m (x17 over 37m) kubelet Readiness probe failed: Get "http://10.0.0.148:9440/readyz": dial tcp 10.0.0.148:9440: connect: connection refused