Name: capo-controller-manager-6975759b4b-84rv8 Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.41 Start Time: Fri, 06 Mar 2026 01:20:07 +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.142 IPs: IP: 10.0.0.142 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://19821946121d8e0a3e628246b7daaf4828ec7657ba8c6f4f027d571b41b77499 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: Fri, 06 Mar 2026 01:29:12 +0000 Last State: Terminated Reason: Error Message: E0306 01:27:48.817783 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: Fri, 06 Mar 2026 01:27:18 +0000 Finished: Fri, 06 Mar 2026 01:27:48 +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-5j7jq (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-5j7jq: 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 36m default-scheduler Successfully assigned capo-system/capo-controller-manager-6975759b4b-84rv8 to instance Warning Unhealthy 32m (x3 over 33m) kubelet Liveness probe failed: Get "http://10.0.0.142:9440/healthz": dial tcp 10.0.0.142:9440: connect: connection refused Normal Pulled 32m (x2 over 36m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Warning Unhealthy 32m (x7 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.142:9440/readyz": dial tcp 10.0.0.142:9440: connect: connection refused Normal Created 32m (x2 over 36m) kubelet Created container manager Normal Started 32m (x2 over 36m) kubelet Started container manager Normal Killing 31m (x2 over 32m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 31m (x5 over 32m) kubelet Readiness probe failed: Get "http://10.0.0.142:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 31m (x3 over 32m) kubelet Liveness probe failed: Get "http://10.0.0.142:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)