Name:                 etcd-controller-2
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 controller-2/199.19.213.121
Start Time:           Sat, 18 Apr 2026 17:54:09 +0000
Labels:               component=etcd
                      tier=control-plane
Annotations:          kubeadm.kubernetes.io/etcd.advertise-client-urls: https://199.19.213.121:2379
                      kubernetes.io/config.hash: 8692d685abff126f85fbddd15703e31e
                      kubernetes.io/config.mirror: 8692d685abff126f85fbddd15703e31e
                      kubernetes.io/config.seen: 2026-04-18T17:54:09.529950860Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.19.213.121
IPs:
  IP:           199.19.213.121
Controlled By:  Node/controller-2
Containers:
  etcd:
    Container ID:  containerd://c5183976280d2a8ac599c7844d5704e6d8661d44b41d9537bd64b6cfb2c7fbaf
    Image:         registry.k8s.io/etcd:3.6.4-0
    Image ID:      registry.k8s.io/etcd@sha256:e36c081683425b5b3bc1425bc508b37e7107bb65dfa9367bf5a80125d431fa19
    Port:          2381/TCP (probe-port)
    Host Port:     2381/TCP (probe-port)
    Command:
      etcd
      --advertise-client-urls=https://199.19.213.121:2379
      --cert-file=/etc/kubernetes/pki/etcd/server.crt
      --client-cert-auth=true
      --data-dir=/var/lib/etcd
      --feature-gates=InitialCorruptCheck=true
      --initial-advertise-peer-urls=https://199.19.213.121:2380
      --initial-cluster=controller-2=https://199.19.213.121:2380,controller-1=https://199.19.213.242: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.121:2379
      --listen-metrics-urls=http://127.0.0.1:2381
      --listen-peer-urls=https://199.19.213.121: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
      --watch-progress-notify-interval=5s
    State:          Running
      Started:      Sat, 18 Apr 2026 17:54:12 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
      memory:     100Mi
    Liveness:     http-get http://127.0.0.1:probe-port/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get http://127.0.0.1:probe-port/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get http://127.0.0.1:probe-port/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
  ----     ------     ----   ----     -------
  Normal   Pulled     5m     kubelet  Container image "registry.k8s.io/etcd:3.6.4-0" already present on machine
  Normal   Created    5m     kubelet  Created container: etcd
  Normal   Started    5m     kubelet  Started container etcd
  Warning  Unhealthy  2m46s  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 503