Name:                 kube-scheduler-controller-2
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 controller-2/199.19.213.99
Start Time:           Mon, 08 Jun 2026 16:02:51 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 44b821b469dfbef2469fa7aa6fa56b91
                      kubernetes.io/config.mirror: 44b821b469dfbef2469fa7aa6fa56b91
                      kubernetes.io/config.seen: 2026-06-08T16:02:51.107771084Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.19.213.99
IPs:
  IP:           199.19.213.99
Controlled By:  Node/controller-2
Containers:
  kube-scheduler:
    Container ID:  containerd://7611e65ee41814bf83ef3912573d853b9a408b3ba956b12930da9475d5aa038d
    Image:         registry.k8s.io/kube-scheduler:v1.34.0
    Image ID:      registry.k8s.io/kube-scheduler@sha256:8fbe6d18415c8af9b31e177f6e444985f3a87349e083fe6eadd36753dddb17ff
    Port:          10259/TCP (probe-port)
    Host Port:     10259/TCP (probe-port)
    Command:
      kube-scheduler
      --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
      --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
      --bind-address=0.0.0.0
      --kubeconfig=/etc/kubernetes/scheduler.conf
      --leader-elect=true
      --tls-min-version=VersionTLS13
    State:          Running
      Started:      Mon, 08 Jun 2026 16:02:52 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
    Liveness:     http-get https://:probe-port/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get https://:probe-port/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get https://:probe-port/livez delay=10s timeout=15s period=10s #success=1 #failure=24
    Environment:  <none>
    Mounts:
      /etc/kubernetes/scheduler.conf from kubeconfig (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True 
  Initialized                 True 
  Ready                       True 
  ContainersReady             True 
  PodScheduled                True 
Volumes:
  kubeconfig:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/kubernetes/scheduler.conf
    HostPathType:  FileOrCreate
QoS Class:         Burstable
Node-Selectors:    <none>
Tolerations:       :NoExecute op=Exists
Events:
  Type     Reason     Age                     From     Message
  ----     ------     ----                    ----     -------
  Normal   Pulled     2m53s                   kubelet  Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine
  Normal   Created    2m53s                   kubelet  Created container: kube-scheduler
  Normal   Started    2m52s                   kubelet  Started container kube-scheduler
  Warning  Unhealthy  2m13s (x25 over 2m37s)  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 500