Name: capo-controller-manager-6975759b4b-l2rwh Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.78 Start Time: Tue, 31 Mar 2026 05:54:58 +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.175 IPs: IP: 10.0.0.175 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://e30452fd2a0884ff7259f0388f47cdc62207e824df3e55ef524ec8d27722dd4a 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: Tue, 31 Mar 2026 06:01:32 +0000 Last State: Terminated Reason: Error Message: E0331 06:01:16.136870 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: Tue, 31 Mar 2026 06:01:16 +0000 Finished: Tue, 31 Mar 2026 06:01:16 +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: 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-55w8x (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-55w8x: 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 37m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-l2rwh to instance Normal Killing 33m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 32m (x2 over 37m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Normal Created 32m (x2 over 37m) kubelet Created container manager Normal Started 32m (x2 over 37m) kubelet Started container manager Warning Unhealthy 32m (x15 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.175:9440/readyz": dial tcp 10.0.0.175:9440: connect: connection refused Warning Unhealthy 32m (x4 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.175:9440/healthz": dial tcp 10.0.0.175:9440: connect: connection refused