Name:             capi-controller-manager-6cf4cfd5b-5kmt5
Namespace:        capi-system
Priority:         0
Service Account:  capi-manager
Node:             controller/199.19.213.10
Start Time:       Mon, 08 Jun 2026 07:51:23 +0000
Labels:           cluster.x-k8s.io/provider=cluster-api
                  control-plane=controller-manager
                  pod-template-hash=6cf4cfd5b
Annotations:      <none>
Status:           Running
SeccompProfile:   RuntimeDefault
IP:               172.24.0.102
IPs:
  IP:           172.24.0.102
Controlled By:  ReplicaSet/capi-controller-manager-6cf4cfd5b
Containers:
  manager:
    Container ID:  containerd://0bb8323f572254cfe0f4bfa1c970df30b736f9dafd0a44af385bb44f2557813c
    Image:         registry.k8s.io/cluster-api/cluster-api-controller:v1.9.6
    Image ID:      registry.k8s.io/cluster-api/cluster-api-controller@sha256:431e1f5c3231bca4153be546a2a6feb6a945fe4ab91540e672532bb38f38d38a
    Ports:         9443/TCP (webhook-server), 9440/TCP (healthz), 8443/TCP (metrics)
    Host Ports:    0/TCP (webhook-server), 0/TCP (healthz), 0/TCP (metrics)
    Command:
      /manager
    Args:
      --leader-elect
      --diagnostics-address=:8443
      --insecure-diagnostics=false
      --use-deprecated-infra-machine-naming=false
      --feature-gates=MachinePool=true,ClusterResourceSet=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true
    State:          Running
      Started:      Mon, 08 Jun 2026 07:51:23 +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:
      POD_NAMESPACE:  capi-system (v1:metadata.namespace)
      POD_NAME:       capi-controller-manager-6cf4cfd5b-5kmt5 (v1:metadata.name)
      POD_UID:         (v1:metadata.uid)
    Mounts:
      /tmp/k8s-webhook-server/serving-certs from cert (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-8ck87 (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:  capi-webhook-service-cert
    Optional:    false
  kube-api-access-8ck87:
    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  82s   default-scheduler  Successfully assigned capi-system/capi-controller-manager-6cf4cfd5b-5kmt5 to controller
  Normal  Pulled     82s   kubelet            Container image "registry.k8s.io/cluster-api/cluster-api-controller:v1.9.6" already present on machine
  Normal  Created    82s   kubelet            Created container: manager
  Normal  Started    82s   kubelet            Started container manager