Name: capi-controller-manager-bc4cf8c95-dzvdv Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/162.253.55.186 Start Time: Tue, 26 May 2026 21:23:38 +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.161 IPs: IP: 10.0.0.161 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://c6ea36f01cda123fe0421e146374f79747ff4809e781be279707d86df7596b01 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, 26 May 2026 21:32:49 +0000 Last State: Terminated Reason: Error Message: W0526 21:32:20.971356 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0526 21:32:20.971861 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0526 21:32:20.971908 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false I0526 21:32:20.971945 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0526 21:32:20.971965 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false Exit Code: 2 Started: Tue, 26 May 2026 21:32:20 +0000 Finished: Tue, 26 May 2026 21:32:48 +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-dzvdv (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-dskfh (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-dskfh: 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-dzvdv to instance 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 36m (x2 over 41m) kubelet Created container manager Normal Started 36m (x2 over 41m) kubelet Started container manager Warning Unhealthy 35m kubelet Readiness probe failed: Get "http://10.0.0.161:9440/readyz": read tcp 10.0.0.244:34820->10.0.0.161:9440: read: connection reset by peer Warning Unhealthy 35m kubelet Liveness probe failed: Get "http://10.0.0.161:9440/healthz": read tcp 10.0.0.244:34832->10.0.0.161:9440: read: connection reset by peer Warning Unhealthy 34m (x5 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.161:9440/healthz": dial tcp 10.0.0.161:9440: connect: connection refused Normal Killing 34m (x2 over 36m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 34m (x11 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.161:9440/readyz": dial tcp 10.0.0.161:9440: connect: connection refused