Name: capo-controller-manager-6975759b4b-5cz6b Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/162.253.55.200 Start Time: Thu, 26 Feb 2026 02:32:19 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=6975759b4b Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.163 IPs: IP: 10.0.0.163 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://bbc869bc98f1294f3dd70856b85ba2844e0265afb495a1aa7de633d8a108a544 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:237da708e483aa8c39766a217d25e45de52816d446764569c77550e6f56f0970 Ports: 9443/TCP, 9440/TCP Host Ports: 0/TCP, 0/TCP Command: /manager Args: --leader-elect --v=2 --diagnostics-address=127.0.0.1:8080 --insecure-diagnostics=true State: Running Started: Thu, 26 Feb 2026 02:50:29 +0000 Last State: Terminated Reason: Error Message: E0226 02:45:14.944202 1 main.go:328] "unable to create controller" err="failed to get API group resources: unable to retrieve the complete list of server APIs: ipam.cluster.x-k8s.io/v1beta1: Get \"https://10.96.0.1:443/apis/ipam.cluster.x-k8s.io/v1beta1\": dial tcp 10.96.0.1:443: connect: connection refused" logger="setup" controller="FloatingIPPool" Exit Code: 1 Started: Thu, 26 Feb 2026 02:45:14 +0000 Finished: Thu, 26 Feb 2026 02:45:15 +0000 Ready: True Restart Count: 4 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: CLUSTER_API_OPENSTACK_INSTANCE_CREATE_TIMEOUT: 10 Mounts: /tmp/k8s-webhook-server/serving-certs from cert (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-f98gf (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: cert: Type: Secret (a volume populated by a Secret) SecretName: capo-webhook-service-cert Optional: false kube-api-access-f98gf: 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 48m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-5cz6b to instance Normal Created 43m (x2 over 48m) kubelet Created container manager Normal Started 43m (x2 over 48m) kubelet Started container manager Warning Unhealthy 41m (x12 over 45m) kubelet Readiness probe failed: Get "http://10.0.0.163:9440/readyz": dial tcp 10.0.0.163:9440: connect: connection refused Warning Unhealthy 41m (x4 over 45m) kubelet Liveness probe failed: Get "http://10.0.0.163:9440/healthz": dial tcp 10.0.0.163:9440: connect: connection refused Warning Failed 39m kubelet Error: context deadline exceeded Normal Pulled 39m (x4 over 48m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Failed 38m kubelet Error: failed to reserve container name "manager_capo-controller-manager-6975759b4b-5cz6b_capo-system_8c8b2b5a-395f-4882-9f36-a7301689cdf2_2": name "manager_capo-controller-manager-6975759b4b-5cz6b_capo-system_8c8b2b5a-395f-4882-9f36-a7301689cdf2_2" is reserved for "e0a248cce490f0dc18db18e06a607d81c60da360072492d1b231d530c9ea45c4" Warning BackOff 33m (x19 over 37m) kubelet Back-off restarting failed container manager in pod capo-controller-manager-6975759b4b-5cz6b_capo-system(8c8b2b5a-395f-4882-9f36-a7301689cdf2)