Name:             capo-controller-manager-6488d4c7c5-vbrkh
Namespace:        capo-system
Priority:         0
Service Account:  capo-manager
Node:             controller/199.204.45.6
Start Time:       Mon, 30 Mar 2026 16:51:24 +0000
Labels:           cluster.x-k8s.io/provider=infrastructure-openstack
                  control-plane=capo-controller-manager
                  pod-template-hash=6488d4c7c5
Annotations:      <none>
Status:           Running
SeccompProfile:   RuntimeDefault
IP:               172.24.0.182
IPs:
  IP:           172.24.0.182
Controlled By:  ReplicaSet/capo-controller-manager-6488d4c7c5
Containers:
  manager:
    Container ID:  containerd://f616c59bda17051689f3c50173f50d6a1dca24fe98c6e511aa28b8774a5547b3
    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:      Mon, 30 Mar 2026 16:51:25 +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-b7769 (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-b7769:
    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  70s   default-scheduler  Successfully assigned capo-system/capo-controller-manager-6488d4c7c5-vbrkh to controller
  Normal   Pulled     71s   kubelet            Container image "registry.k8s.io/capi-openstack/capi-openstack-controller:v0.12.4" already present on machine
  Normal   Created    71s   kubelet            Created container: manager
  Normal   Started    70s   kubelet            Started container manager
  Warning  Unhealthy  70s   kubelet            Readiness probe failed: Get "http://172.24.0.182:9440/readyz": dial tcp 172.24.0.182:9440: connect: connection refused