Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.204.45.235
Start Time:           Mon, 11 May 2026 05:38:32 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.seen: 2026-05-11T05:38:23.936868066Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.235
IPs:
  IP:           199.204.45.235
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://a7db34f739e8c23d6d8778af5491cb0e1c3ed3b2742b1272a500a45456e2d039
    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:      Mon, 11 May 2026 06:27:27 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Mon, 11 May 2026 06:26:15 +0000
      Finished:     Mon, 11 May 2026 06:27:03 +0000
    Ready:          True
    Restart Count:  3
    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    30m (x2 over 30m)  kubelet  Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(52c03224580ac568b66c5ffba7a99547)
  Warning  Unhealthy  29m                kubelet  Liveness probe failed: Get "https://199.204.45.235:10259/healthz": read tcp 199.204.45.235:58666->199.204.45.235:10259: read: connection reset by peer
  Warning  Unhealthy  28m (x4 over 30m)  kubelet  Liveness probe failed: Get "https://199.204.45.235:10259/healthz": dial tcp 199.204.45.235:10259: connect: connection refused
  Normal   Pulled     28m (x3 over 30m)  kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    28m (x3 over 30m)  kubelet  Created container kube-scheduler
  Normal   Started    28m (x3 over 30m)  kubelet  Started container kube-scheduler