Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.204.45.227
Start Time:           Mon, 08 Jun 2026 08:44:08 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: fe5040a26333b04853e6546e7683a847
                      kubernetes.io/config.mirror: fe5040a26333b04853e6546e7683a847
                      kubernetes.io/config.seen: 2026-06-08T08:44:07.913425857Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.227
IPs:
  IP:           199.204.45.227
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://367b126daf6c0d452b824b175e45687a1fe4dc05f38f875dc09c62188f344752
    Image:         harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.32.10
    Image ID:      harbor.atmosphere.dev/registry.k8s.io/kube-scheduler@sha256:9c58e1adcad5af66d1d9ca5cf9a4c266e4054b8f19f91a8fff1993549e657b10
    Port:          <none>
    Host Port:     <none>
    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 08:44:03 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
    Liveness:     http-get https://:10259/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get https://:10259/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get https://:10259/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
  ----     ------     ----   ----     -------
  Warning  Unhealthy  7m15s  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 500