Name: capo-controller-manager-6975759b4b-hc6dz Namespace: capo-system Priority: 0 Service Account: capo-manager Node: instance/199.19.213.11 Start Time: Fri, 10 Apr 2026 14:51:31 +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.45 IPs: IP: 10.0.0.45 Controlled By: ReplicaSet/capo-controller-manager-6975759b4b Containers: manager: Container ID: containerd://38b53a1bc296e7a47505ed89c805d79c1fd32df231afa5e87af33899864e78fb 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, 10 Apr 2026 15:01:01 +0000 Last State: Terminated Reason: Error Message: E0410 14:59:20.938485 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: forbidden: User \"system:serviceaccount:capo-system:capo-manager\" cannot get path \"/apis/ipam.cluster.x-k8s.io/v1beta1\"" logger="setup" controller="FloatingIPPool" Exit Code: 1 Started: Fri, 10 Apr 2026 14:59:18 +0000 Finished: Fri, 10 Apr 2026 14:59:20 +0000 Ready: True Restart Count: 2 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-zqrtr (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-zqrtr: 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-hc6dz to instance Normal Killing 34m kubelet Container manager failed liveness probe, will be restarted Normal Pulled 32m (x2 over 40m) 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 40m) kubelet Created container manager Normal Started 32m (x2 over 40m) kubelet Started container manager Warning Unhealthy 32m kubelet Readiness probe failed: Get "http://10.0.0.45:9440/readyz": read tcp 10.0.0.77:54344->10.0.0.45:9440: read: connection reset by peer Warning Unhealthy 32m (x14 over 34m) kubelet Readiness probe failed: Get "http://10.0.0.45:9440/readyz": dial tcp 10.0.0.45:9440: connect: connection refused Warning Unhealthy 32m (x4 over 34m) kubelet Liveness probe failed: Get "http://10.0.0.45:9440/healthz": dial tcp 10.0.0.45:9440: connect: connection refused