Name: capo-controller-manager-6488d4c7c5-vnq4x Namespace: capo-system Priority: 0 Service Account: capo-manager Node: controller/199.204.45.233 Start Time: Wed, 01 Apr 2026 10:20:13 +0000 Labels: cluster.x-k8s.io/provider=infrastructure-openstack control-plane=capo-controller-manager pod-template-hash=6488d4c7c5 Annotations: Status: Running SeccompProfile: RuntimeDefault IP: 172.24.0.243 IPs: IP: 172.24.0.243 Controlled By: ReplicaSet/capo-controller-manager-6488d4c7c5 Containers: manager: Container ID: containerd://63f3c25d9c86b5a9a1404ae91c35947e662122eaba9865c2af816a0e1c3ea269 Image: registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4 Image ID: registry.k8s.io/capi-openstack/capi-openstack-controller@sha256:237da708e483aa8c39766a217d25e45de52816d446764569c77550e6f56f0970 Ports: 9443/TCP (webhook-server), 9440/TCP (healthz) Host Ports: 0/TCP (webhook-server), 0/TCP (healthz) Command: /manager Args: --leader-elect --v=2 --diagnostics-address=127.0.0.1:8080 --insecure-diagnostics=true State: Running Started: Wed, 01 Apr 2026 10:20:14 +0000 Ready: True Restart Count: 0 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-md454 (ro) Conditions: Type Status PodReadyToStartContainers True 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-md454: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt Optional: false DownwardAPI: true QoS Class: BestEffort Node-Selectors: kubernetes.io/os=linux 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 66s default-scheduler Successfully assigned capo-system/capo-controller-manager-6488d4c7c5-vnq4x to controller Normal Pulled 65s kubelet Container image "registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine Normal Created 65s kubelet Created container: manager Normal Started 65s kubelet Started container manager