Name:                 kube-scheduler-instance
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 instance/199.204.45.65
Start Time:           Fri, 14 Aug 2026 02:05:25 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547
                      kubernetes.io/config.seen: 2026-08-14T02:05:25.858537937Z
                      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://04edb505d3060a18739dcc507e615ba2f44e51cd328fac7cdc5b96f5267689eb
    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, 14 Aug 2026 02:56:11 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Fri, 14 Aug 2026 02:20:41 +0000
      Finished:     Fri, 14 Aug 2026 02:56:10 +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     53m                    kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    53m                    kubelet  Created container kube-scheduler
  Normal   Started    53m                    kubelet  Started container kube-scheduler
  Warning  Unhealthy  37m (x2 over 38m)      kubelet  Liveness probe failed: Get "https://199.204.45.65:10259/healthz": dial tcp 199.204.45.65:10259: connect: connection refused
  Warning  Unhealthy  2m19s (x3 over 2m39s)  kubelet  Liveness probe failed: Get "https://199.204.45.65:10259/healthz": net/http: TLS handshake timeout
  Warning  Unhealthy  2m18s                  kubelet  Liveness probe failed: Get "https://199.204.45.65:10259/healthz": read tcp 199.204.45.65:54794->199.204.45.65:10259: read: connection reset by peer
  Normal   Pulled     2m17s (x2 over 37m)    kubelet  Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine
  Normal   Created    2m17s (x2 over 37m)    kubelet  Created container kube-scheduler
  Normal   Started    2m17s (x2 over 37m)    kubelet  Started container kube-scheduler