Name: capo-controller-manager-6975759b4b-ng667 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.78 Start Time: Wed, 04 Mar 2026 02:13:43 +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.19 IPs: IP: 10.0.0.19 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://5d38ad1d426f3d4121a2eed26b510fdc5786ad297e58ecebbc7eaf72a5ac866d 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: Wed, 04 Mar 2026 02:23:01 +0000 Last State: Terminated Reason: Error Message: E0304 02:22:06.589274 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: i/o timeout" logger="setup" controller="FloatingIPPool" Exit Code: 1 Started: Wed, 04 Mar 2026 02:21:36 +0000 Finished: Wed, 04 Mar 2026 02:22:06 +0000 Ready: True Restart Count: 5 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-nqthz (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-nqthz: 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 capo-system/capo-controller-manager-6975759b4b-ng667 to instance Normal Pulled 37m (x2 over 40m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 37m (x3 over 37m) kubelet Liveness probe failed: Get "http://10.0.0.19:9440/healthz": dial tcp 10.0.0.19:9440: connect: connection refused Normal Killing 37m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 35m (x14 over 37m) kubelet Readiness probe failed: Get "http://10.0.0.19:9440/readyz": dial tcp 10.0.0.19:9440: connect: connection refused Normal Created 35m (x2 over 40m) kubelet Created container manager Normal Started 35m (x2 over 40m) kubelet Started container manager Warning Unhealthy 35m (x2 over 35m) kubelet Readiness probe failed: Get "http://10.0.0.19:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)