Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.204.45.53
Start Time:           Tue, 14 Apr 2026 07:27:43 +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-14T07:27:37.437173646Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.53
IPs:
  IP:           199.204.45.53
Controlled By:  Node/instance
Containers:
  kube-scheduler:
    Container ID:  containerd://d873c6f0cfd2382bc1ccb8ec7b489f8eb7217657537290a70209aa76adb48497
    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, 14 Apr 2026 08:24:29 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 14 Apr 2026 08:22:15 +0000
      Finished:     Tue, 14 Apr 2026 08:24:06 +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  Unhealthy  34m (x14 over 37m)  kubelet  Liveness probe failed: Get "https://199.204.45.53:10259/healthz": dial tcp 199.204.45.53:10259: connect: connection refused
  Normal   Killing    34m                 kubelet  Container kube-scheduler failed liveness probe, will be restarted
  Normal   Created    34m (x2 over 36m)   kubelet  Created container kube-scheduler
  Normal   Started    34m (x2 over 36m)   kubelet  Started container kube-scheduler
  Warning  BackOff    32m (x3 over 32m)   kubelet  Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(52c03224580ac568b66c5ffba7a99547)
  Normal   Pulled     32m (x3 over 36m)   kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine