Name: capo-controller-manager-56cf844ccd-n6k2p Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.204.45.70 Start Time: Fri, 17 Jul 2026 19:02:03 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=56cf844ccd Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 10.0.0.148 IPs: IP: 10.0.0.148 Controlled By: ReplicaSet/capo-controller-manager-56cf844ccd Containers: manager: Container ID: containerd://51f15c6ffdf4a7db2e8dfa0af518796517452b1512337eb2ad3605a97fc1930d Image: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4 Image ID: harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:b428de23d97c69ebb350e2359e73eb6ec92572e5dfab8cc4cea9994c01fa4ee0 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 --feature-gates=PriorityQueue=false,AutoScaleFromZero=false State: Running Started: Fri, 17 Jul 2026 19:09:44 +0000 Last State: Terminated Reason: Error Message: I0717 19:09:24.068011 1 main.go:252] "Feature gates: AutoScaleFromZero=false,PriorityQueue=false\n" logger="setup" I0717 19:09:24.068356 1 envvar.go:172] "Feature gate default state" feature="ClientsPreferCBOR" enabled=false I0717 19:09:24.068388 1 envvar.go:172] "Feature gate default state" feature="InOrderInformers" enabled=true I0717 19:09:24.068397 1 envvar.go:172] "Feature gate default state" feature="InformerResourceVersion" enabled=false I0717 19:09:24.068405 1 envvar.go:172] "Feature gate default state" feature="WatchListClient" enabled=false I0717 19:09:24.068416 1 envvar.go:172] "Feature gate default state" feature="ClientsAllowCBOR" enabled=false E0717 19:09:24.070801 1 main.go:388] "unable to create controller" err="failed to get server groups: Get \"https://10.96.0.1:443/api\": dial tcp 10.96.0.1:443: connect: connection refused" logger="setup" controller="FloatingIPPool" Exit Code: 1 Started: Fri, 17 Jul 2026 19:09:23 +0000 Finished: Fri, 17 Jul 2026 19:09:24 +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-pr7mc (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-pr7mc: 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-56cf844ccd-n6k2p to instance Normal Pulled 37m kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/capi-openstack/capi-openstack-controller:v0.14.4" already present on machine Normal Created 37m kubelet Created container manager Normal Started 37m kubelet Started container manager Warning Unhealthy 34m (x2 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.148:9440/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 34m (x2 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.148:9440/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 33m kubelet Liveness probe failed: Get "http://10.0.0.148:9440/healthz": dial tcp 10.0.0.148:9440: connect: connection refused Normal Killing 32m (x5 over 33m) kubelet Container manager failed liveness probe, will be restarted Warning Unhealthy 32m (x13 over 33m) kubelet Readiness probe failed: Get "http://10.0.0.148:9440/readyz": dial tcp 10.0.0.148:9440: connect: connection refused