Name:                 kube-scheduler-controller-3
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 controller-3/199.204.45.248
Start Time:           Sat, 18 Apr 2026 17:55:04 +0000
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 04e5548fe5f390a30f949b23eb774eca
                      kubernetes.io/config.mirror: 04e5548fe5f390a30f949b23eb774eca
                      kubernetes.io/config.seen: 2026-04-18T17:55:03.832645703Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   199.204.45.248
IPs:
  IP:           199.204.45.248
Controlled By:  Node/controller-3
Containers:
  kube-scheduler:
    Container ID:  containerd://67ee31737759ae9c869f5689de5aba7372640672b0a38ba6cf55bf4c5ef4e03c
    Image:         registry.k8s.io/kube-scheduler:v1.33.4
    Image ID:      registry.k8s.io/kube-scheduler@sha256:71533e5a960e2955a54164905e92dac516ec874a23e0bf31304db82650101a4a
    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:      Sat, 18 Apr 2026 17:55:05 +0000
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
    Liveness:     http-get https://:10259/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get https://:10259/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get https://:10259/livez delay=10s timeout=15s period=10s #success=1 #failure=24
    Environment:  <none>
    Mounts:
      /etc/kubernetes/scheduler.conf from kubeconfig (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True 
  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     2m9s                 kubelet  Container image "registry.k8s.io/kube-scheduler:v1.33.4" already present on machine
  Normal   Created    2m9s                 kubelet  Created container: kube-scheduler
  Normal   Started    2m8s                 kubelet  Started container kube-scheduler
  Warning  Unhealthy  116s (x2 over 117s)  kubelet  Readiness probe failed: HTTP probe failed with statuscode: 500