Name: capo-controller-manager-65565fdb7f-lbr7z Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.223 Start Time: Thu, 07 May 2026 03:02:13 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=65565fdb7f Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.15 IPs: IP: 10.0.0.15 Controlled By: ReplicaSet/capo-controller-manager-65565fdb7f Containers: manager: Container ID: containerd://0aa518583f3a1226f95b1262db8973fe06c7834bbb376b28acafaa51969f6859 Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b964c2f374ad4f26a593749d3c737492d5c1821db143b26596c9285b9055a8b4 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, 07 May 2026 03:15:34 +0000 Last State: Terminated Reason: Error Message: E0507 03:14:13.371034 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: Thu, 07 May 2026 03:13:43 +0000 Finished: Thu, 07 May 2026 03:14:13 +0000 Ready: True Restart Count: 6 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-cbnbq (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-cbnbq: 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 43m default-scheduler Successfully assigned capo-system/capo-controller-manager-65565fdb7f-lbr7z to instance Warning Unhealthy 39m (x3 over 40m) kubelet Liveness probe failed: Get "http://10.0.0.15:9440/healthz": dial tcp 10.0.0.15:9440: connect: connection refused Normal Killing 39m kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 38m (x10 over 40m) kubelet Readiness probe failed: Get "http://10.0.0.15:9440/readyz": dial tcp 10.0.0.15:9440: connect: connection refused Normal Pulled 38m (x2 over 43m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.7" already present on machine Normal Created 38m (x2 over 43m) kubelet Created container manager Normal Started 38m (x2 over 43m) kubelet Started container manager Warning Unhealthy 38m (x5 over 38m) kubelet Readiness probe failed: Get "http://10.0.0.15:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m (x9 over 38m) kubelet Liveness probe failed: Get "http://10.0.0.15:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)