Name: kube-scheduler-controller-3 Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: controller-3/199.204.45.244 Start Time: Sat, 09 May 2026 13:11:13 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 3011c9e0d98f466e5b99957787f12599 kubernetes.io/config.mirror: 3011c9e0d98f466e5b99957787f12599 kubernetes.io/config.seen: 2026-05-09T13:11:12.849858501Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.204.45.244 IPs: IP: 199.204.45.244 Controlled By: Node/controller-3 Containers: kube-scheduler: Container ID: containerd://48ab2606debe5e208cb584b8f53e295b296f47879ed8f69070862ce9c619f978 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: Sat, 09 May 2026 13:11:14 +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: