Name:                 kube-scheduler-controller
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 controller/199.204.45.205
Start Time:           Sat, 09 May 2026 13:10:53 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 533f943efad0a8211a54e7f55baaac1f
                      kubernetes.io/config.mirror: 533f943efad0a8211a54e7f55baaac1f
                      kubernetes.io/config.seen: 2026-05-09T13:10:46.530508671Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.205
IPs:
  IP:           199.204.45.205
Controlled By:  Node/controller
Containers:
  kube-scheduler:
    Container ID:  containerd://1d39c1721c25c786c5de26391ef5582287a7ed0283f367e5b2a2f92681cc1cf5
    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:      Sat, 09 May 2026 13:10:48 +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     4m1s   kubelet  Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine
  Normal   Created    4m     kubelet  Created container: kube-scheduler
  Normal   Started    4m     kubelet  Started container kube-scheduler
  Warning  Unhealthy  3m54s  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 500