Name:                 kube-scheduler-minikube
Namespace:            kube-system
Priority:             2000001000
Priority Class Name:  system-node-critical
Node:                 minikube/192.168.49.2
Start Time:           Fri, 12 Jun 2026 20:03:37 -0400
Labels:               component=kube-scheduler
                      tier=control-plane
Annotations:          kubernetes.io/config.hash: 8daa088f69073e52aa45acdea43d1d39
                      kubernetes.io/config.mirror: 8daa088f69073e52aa45acdea43d1d39
                      kubernetes.io/config.seen: 2026-06-13T00:03:37.856884853Z
                      kubernetes.io/config.source: file
Status:               Running
SeccompProfile:       RuntimeDefault
IP:                   192.168.49.2
IPs:
  IP:           192.168.49.2
Controlled By:  Node/minikube
Containers:
  kube-scheduler:
    Container ID:  cri-o://586a027786cfbb1388c6604c9724230568325d33c0533fabdc1102ca27f13504
    Image:         registry.k8s.io/kube-scheduler:v1.32.5
    Image ID:      registry.k8s.io/kube-scheduler@sha256:b625d6fcca62cb4c867a1dec871add6ef16741d0d4632ba47e0f5f2b2b89c2a0
    Port:          <none>
    Host Port:     <none>
    Command:
      kube-scheduler
      --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
      --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
      --bind-address=127.0.0.1
      --kubeconfig=/etc/kubernetes/scheduler.conf
      --leader-elect=false
    State:          Running
      Started:      Fri, 12 Jun 2026 20:03:33 -0400
    Ready:          True
    Restart Count:  0
    Requests:
      cpu:        100m
    Liveness:     http-get https://127.0.0.1:10259/livez delay=10s timeout=15s period=10s #success=1 #failure=8
    Readiness:    http-get https://127.0.0.1:10259/readyz delay=0s timeout=15s period=1s #success=1 #failure=3
    Startup:      http-get https://127.0.0.1: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     20m   kubelet  spec.containers{kube-scheduler}: Container image "registry.k8s.io/kube-scheduler:v1.32.5" already present on machine
  Normal   Created    20m   kubelet  spec.containers{kube-scheduler}: Created container: kube-scheduler
  Normal   Started    20m   kubelet  spec.containers{kube-scheduler}: Started container kube-scheduler
  Warning  Unhealthy  20m   kubelet  spec.containers{kube-scheduler}: Readiness probe failed: HTTP probe failed with statuscode: 500