Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/162.253.55.207
Start Time:           Wed, 04 Feb 2026 05:15:31 +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-04T05:15:30.855350000Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   162.253.55.207
IPs:
  IP:           162.253.55.207
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://06753a81e7175a5f3b633124e3b3cadb34b5b1f2d7af5068fbbb9e159be0a03b
    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:      Wed, 04 Feb 2026 05:18:15 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 04 Feb 2026 05:15:25 +0000
      Finished:     Wed, 04 Feb 2026 05:17:43 +0000
    Ready:          True
    Restart Count:  1
    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     6m58s                  kubelet  Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    6m58s                  kubelet  Created container kube-scheduler
  Normal   Started    6m57s                  kubelet  Started container kube-scheduler
  Warning  Unhealthy  4m21s (x2 over 4m31s)  kubelet  Liveness probe failed: Get "https://162.253.55.207:10259/healthz": dial tcp 162.253.55.207:10259: connect: connection refused
  Normal   Pulled     4m13s                  kubelet  Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    4m7s                   kubelet  Created container kube-scheduler
  Normal   Started    4m5s                   kubelet  Started container kube-scheduler