Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.19.213.134
Start Time:           Tue, 21 Apr 2026 17:15:31 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.seen: 2026-04-21T17:15:12.190767815Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.19.213.134
IPs:
  IP:           199.19.213.134
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://eed72fb406d0195ed7f0a6e6e957fcf9c477269e8a7f7fe060108294e2c3e441
    Image:         harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13
    Image ID:      harbor.atmosphere.dev/registry.k8s.io/kube-scheduler@sha256:efeb791718f4b9c62bd683f5b403da520f3651cb36ad9f800e0f98b595beafa4
    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:      Tue, 21 Apr 2026 18:29:40 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 21 Apr 2026 18:24:19 +0000
      Finished:     Tue, 21 Apr 2026 18:26:50 +0000
    Ready:          True
    Restart Count:  6
    Requests:
      cpu:        100m
    Liveness:     http-get https://:10259/healthz delay=10s timeout=15s period=10s #success=1 #failure=8
    Startup:      http-get https://:10259/healthz delay=10s timeout=15s period=10s #success=1 #failure=24
    Environment:  <none>
    Mounts:
      /etc/kubernetes/scheduler.conf from kubeconfig (ro)
Conditions:
  Type              Status
  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  BackOff    6m54s (x3 over 7m2s)  kubelet  Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(52c03224580ac568b66c5ffba7a99547)
  Normal   Created    6m38s (x5 over 68m)   kubelet  Created container kube-scheduler
  Normal   Started    6m38s (x5 over 68m)   kubelet  Started container kube-scheduler
  Warning  Unhealthy  2m54s (x15 over 68m)  kubelet  Liveness probe failed: Get "https://199.19.213.134:10259/healthz": dial tcp 199.19.213.134:10259: connect: connection refused
  Normal   Killing    2m54s                 kubelet  Container kube-scheduler failed liveness probe, will be restarted
  Normal   Pulled     78s (x6 over 68m)     kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine