Name: kube-scheduler-controller-2 Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: controller-2/199.204.45.233 Start Time: Mon, 30 Mar 2026 20:21:20 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: f8263deeab4f24c8f48312e025458923 kubernetes.io/config.mirror: f8263deeab4f24c8f48312e025458923 kubernetes.io/config.seen: 2026-03-30T20:21:20.215901507Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.204.45.233 IPs: IP: 199.204.45.233 Controlled By: Node/controller-2 Containers: kube-scheduler: Container ID: containerd://1fd0b5405a99d54a2498dff6509ce9fb3e08717d0d8a0e10fd382ebbdf2fe822 Image: registry.k8s.io/kube-scheduler:v1.33.4 Image ID: registry.k8s.io/kube-scheduler@sha256:71533e5a960e2955a54164905e92dac516ec874a23e0bf31304db82650101a4a Port: Host 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: Mon, 30 Mar 2026 20:21:21 +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: 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: