Name:                 etcd-controller-2
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 controller-2/199.19.213.102
Start Time:           Tue, 17 Mar 2026 20:47:28 +0000
Labels:               component=etcd
                      tier=control-plane
Annotations:          kubeadm.kubernetes.io/etcd.advertise-client-urls: https://199.19.213.102:2379
                      kubernetes.io/config.hash: 9f4c6eb645c22942aaf7135ca55c65dd
                      kubernetes.io/config.mirror: 9f4c6eb645c22942aaf7135ca55c65dd
                      kubernetes.io/config.seen: 2026-03-17T20:47:28.069306600Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.19.213.102
IPs:
  IP:           199.19.213.102
Controlled By:  Node/controller-2
Containers:
  etcd:
    Container ID:  containerd://cd54aefa3f9bbcdbdd91a8b7099cce9ecd36c0dd0b69a1fd769a32b4df710b36
    Image:         registry.k8s.io/etcd:3.5.21-0
    Image ID:      registry.k8s.io/etcd@sha256:d58c035df557080a27387d687092e3fc2b64c6d0e3162dc51453a115f847d121
    Port:          <none>
    Host Port:     <none>
    Command:
      etcd
      --advertise-client-urls=https://199.19.213.102:2379
      --cert-file=/etc/kubernetes/pki/etcd/server.crt
      --client-cert-auth=true
      --data-dir=/var/lib/etcd
      --experimental-initial-corrupt-check=true
      --experimental-watch-progress-notify-interval=5s
      --initial-advertise-peer-urls=https://199.19.213.102:2380
      --initial-cluster=controller-1=https://199.19.213.3:2380,controller-2=https://199.19.213.102:2380
      --initial-cluster-state=existing
      --key-file=/etc/kubernetes/pki/etcd/server.key
      --listen-client-urls=https://127.0.0.1:2379,https://199.19.213.102:2379
      --listen-metrics-urls=http://127.0.0.1:2381
      --listen-peer-urls=https://199.19.213.102:2380
      --name=controller-2
      --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt
      --peer-client-cert-auth=true
      --peer-key-file=/etc/kubernetes/pki/etcd/peer.key
      --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
      --snapshot-count=10000
      --tls-min-version=TLS1.3
      --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt
    State:          Running
      Started:      Tue, 17 Mar 2026 20:47:29 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
      memory:     100Mi
    Liveness:     http-get http://127.0.0.1:2381/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get http://127.0.0.1:2381/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get http://127.0.0.1:2381/readyz delay=10s timeout=15s period=10s #success=1 #failure=24
    Environment:  <none>
    Mounts:
      /etc/kubernetes/pki/etcd from etcd-certs (rw)
      /var/lib/etcd from etcd-data (rw)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True 
  Initialized                 True 
  Ready                       True 
  ContainersReady             True 
  PodScheduled                True 
Volumes:
  etcd-certs:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/pki/etcd
    HostPathType:  DirectoryOrCreate
  etcd-data:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/etcd
    HostPathType:  DirectoryOrCreate
QoS Class:         Burstable
Node-Selectors:    <none>
Tolerations:       :NoExecute op=Exists
Events:
  Type     Reason     Age                From     Message
  ----     ------     ----               ----     -------
  Warning  Unhealthy  25s (x2 over 32s)  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 503