Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.204.45.65
Start Time:           Fri, 24 Apr 2026 03:32:26 +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-24T03:32:06.361608925Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.65
IPs:
  IP:           199.204.45.65
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://1e189b30ea6b44056219c9882fa6a0eef6b01ca6afaef80a1d2959edb2f389c4
    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:      Fri, 24 Apr 2026 03:58:44 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Fri, 24 Apr 2026 03:57:32 +0000
      Finished:     Fri, 24 Apr 2026 03:58:02 +0000
    Ready:          True
    Restart Count:  2
    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
  ----     ------     ----               ----     -------
  Normal   Pulled     46m                kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    46m                kubelet  Created container kube-scheduler
  Normal   Started    46m                kubelet  Started container kube-scheduler
  Warning  Unhealthy  21m                kubelet  Liveness probe failed: Get "https://199.204.45.65:10259/healthz": read tcp 199.204.45.65:39844->199.204.45.65:10259: read: connection reset by peer
  Warning  Unhealthy  20m (x7 over 21m)  kubelet  Liveness probe failed: Get "https://199.204.45.65:10259/healthz": dial tcp 199.204.45.65:10259: connect: connection refused
  Normal   Pulled     20m (x2 over 21m)  kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    20m (x2 over 21m)  kubelet  Created container kube-scheduler
  Normal   Started    20m (x2 over 21m)  kubelet  Started container kube-scheduler