Name: capi-controller-manager-bc4cf8c95-6hkw4 Namespace: capi-system Priority: 0 Service Account: capi-manager Node: instance/199.204.45.216 Start Time: Wed, 03 Jun 2026 00:37:08 +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.202 IPs: IP: 10.0.0.202 Controlled By: ReplicaSet/capi-controller-manager-bc4cf8c95 Containers: manager: Container ID: containerd://162bf9e4cd68d714309488c526194f9dbb3362629b3a300755091d4da43afd69 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: Wed, 03 Jun 2026 00:45:09 +0000 Last State: Terminated Reason: Error Message: W0603 00:44:39.907206 1 feature_gate.go:354] Setting GA feature gate ClusterResourceSet=true. It will be removed in a future release. I0603 00:44:39.907549 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0603 00:44:39.907568 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0603 00:44:39.907572 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0603 00:44:39.907576 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false Exit Code: 2 Started: Wed, 03 Jun 2026 00:44:39 +0000 Finished: Wed, 03 Jun 2026 00:45:08 +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-6hkw4 (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-9rxf8 (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-9rxf8: 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 40m default-scheduler Successfully assigned capi-system/capi-controller-manager-bc4cf8c95-6hkw4 to instance Normal Pulled 35m (x2 over 40m) 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 40m) kubelet Created container manager Normal Started 35m (x2 over 40m) kubelet Started container manager Warning Unhealthy 34m kubelet Liveness probe failed: Get "http://10.0.0.202:9440/healthz": read tcp 10.0.0.4:39828->10.0.0.202:9440: read: connection reset by peer Warning Unhealthy 34m kubelet Readiness probe failed: Get "http://10.0.0.202:9440/readyz": read tcp 10.0.0.4:39824->10.0.0.202:9440: read: connection reset by peer Warning Unhealthy 34m (x11 over 36m) kubelet Readiness probe failed: Get "http://10.0.0.202:9440/readyz": dial tcp 10.0.0.202:9440: connect: connection refused Warning Unhealthy 34m (x5 over 36m) kubelet Liveness probe failed: Get "http://10.0.0.202:9440/healthz": dial tcp 10.0.0.202:9440: connect: connection refused Normal Killing 34m (x2 over 36m) kubelet Container manager failed liveness probe, will be restarted