Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/162.253.55.204
Start Time:           Tue, 24 Feb 2026 06:24:11 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 4cec6c3159d80558328947d0819d07fb
                      kubernetes.io/config.mirror: 4cec6c3159d80558328947d0819d07fb
                      kubernetes.io/config.seen: 2026-02-24T06:24:11.572425176Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   162.253.55.204
IPs:
  IP:           162.253.55.204
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://5c578fd4c8b4b97723102013a3be50c47fa0fea05d94c2a7b38b3bf49a1142c6
    Image:         registry.k8s.io/kube-scheduler:v1.28.13
    Image ID:      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, 24 Feb 2026 07:47:39 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 24 Feb 2026 07:22:26 +0000
      Finished:     Tue, 24 Feb 2026 07:47:02 +0000
    Ready:          True
    Restart Count:  5
    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  Unhealthy  30m (x2 over 31m)    kubelet  Liveness probe failed: Get "https://162.253.55.204:10259/healthz": net/http: TLS handshake timeout
  Warning  Unhealthy  30m                  kubelet  Liveness probe failed: Get "https://162.253.55.204:10259/healthz": read tcp 162.253.55.204:44116->162.253.55.204:10259: read: connection reset by peer
  Warning  BackOff    30m (x5 over 68m)    kubelet  Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(4cec6c3159d80558328947d0819d07fb)
  Warning  Unhealthy  5m32s (x8 over 68m)  kubelet  Liveness probe failed: Get "https://162.253.55.204:10259/healthz": dial tcp 162.253.55.204:10259: connect: connection refused
  Normal   Pulled     5m31s (x5 over 73m)  kubelet  Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    5m14s (x5 over 73m)  kubelet  Created container kube-scheduler
  Normal   Started    5m13s (x5 over 73m)  kubelet  Started container kube-scheduler