Name:             capi-controller-manager-564fbdcdb6-d4nc2
Namespace:        capi-system
Priority:         0
Service Account:  capi-manager
Node:             controller/199.19.213.205
Start Time:       Thu, 25 Jun 2026 19:43:31 +0000
Labels:           cluster.x-k8s.io/provider=cluster-api
                  control-plane=controller-manager
                  pod-template-hash=564fbdcdb6
Annotations:      <none>
Status:           Running
SeccompProfile:   RuntimeDefault
IP:               172.24.0.236
IPs:
  IP:           172.24.0.236
Controlled By:  ReplicaSet/capi-controller-manager-564fbdcdb6
Containers:
  manager:
    Container ID:  containerd://3447a0d792b68071232d2348a7a5fea19c5797472e8d342c3288a588dd148b02
    Image:         registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2
    Image ID:      registry.k8s.io/cluster-api/cluster-api-controller@sha256:e53df33f43352d5e7bf5a72fd4171c1447ef2123a4c551484e45395f3dbb1875
    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
      --feature-gates=MachinePool=true,ClusterTopology=true,RuntimeSDK=false,MachineSetPreflightChecks=true,MachineWaitForVolumeDetachConsiderVolumeAttachments=true,PriorityQueue=true,ReconcilerRateLimiting=true,InPlaceUpdates=false,MachineTaintPropagation=false
    State:          Running
      Started:      Thu, 25 Jun 2026 19:43:32 +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-564fbdcdb6-d4nc2 (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-mltvm (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-mltvm:
    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-564fbdcdb6-d4nc2 to controller
  Normal   Pulled     81s   kubelet            Container image "registry.k8s.io/cluster-api/cluster-api-controller:v1.13.2" already present on machine
  Normal   Created    81s   kubelet            Created container: manager
  Normal   Started    81s   kubelet            Started container manager
  Warning  Unhealthy  81s   kubelet            Readiness probe failed: Get "http://172.24.0.236:9440/readyz": dial tcp 172.24.0.236:9440: connect: connection refused