Name: kube-scheduler-controller Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: controller/162.253.55.200 Start Time: Tue, 31 Mar 2026 00:20:07 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 533f943efad0a8211a54e7f55baaac1f kubernetes.io/config.mirror: 533f943efad0a8211a54e7f55baaac1f kubernetes.io/config.seen: 2026-03-31T00:20:07.435898779Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 162.253.55.200 IPs: IP: 162.253.55.200 Controlled By: Node/controller Containers: kube-scheduler: Container ID: containerd://05115e784a7f35a9328910940ba24d3d10c7a045991f1552a662fdc5f9cc7a66 Image: registry.k8s.io/kube-scheduler:v1.34.0 Image ID: registry.k8s.io/kube-scheduler@sha256:8fbe6d18415c8af9b31e177f6e444985f3a87349e083fe6eadd36753dddb17ff Port: 10259/TCP (probe-port) Host Port: 10259/TCP (probe-port) 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, 31 Mar 2026 00:20:02 +0000 Ready: True Restart Count: 0 Requests: cpu: 100m Liveness: http-get https://:probe-port/livez delay=10s timeout=15s period=10s #success=1 #failure=8 Readiness: http-get https://:probe-port/readyz delay=0s timeout=15s period=1s #success=1 #failure=3 Startup: http-get https://:probe-port/livez delay=10s timeout=15s period=10s #success=1 #failure=24 Environment: 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: Tolerations: :NoExecute op=Exists Events: