Name: kube-scheduler-controller Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: controller/199.204.45.6 Start Time: Mon, 30 Mar 2026 16:45:57 +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-30T16:45:40.666005173Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.204.45.6 IPs: IP: 199.204.45.6 Controlled By: Node/controller Containers: kube-scheduler: Container ID: containerd://9eb4b2a1f99207cf97ef4ce12d12f458807d661210263cdccd135bbbeb40b5fd 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: Mon, 30 Mar 2026 16:47:33 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Mon, 30 Mar 2026 16:46:27 +0000 Finished: Mon, 30 Mar 2026 16:47:15 +0000 Ready: True Restart Count: 2 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: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Pulled 6m58s kubelet Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine Normal Created 6m57s kubelet Created container: kube-scheduler Normal Started 6m57s kubelet Started container kube-scheduler Warning Unhealthy 6m22s kubelet Liveness probe failed: Get "https://199.204.45.6:10259/livez": dial tcp 199.204.45.6:10259: connect: connection refused Warning Unhealthy 5m28s (x7 over 6m25s) kubelet Readiness probe failed: Get "https://199.204.45.6:10259/readyz": dial tcp 199.204.45.6:10259: connect: connection refused Warning BackOff 5m22s (x3 over 5m28s) kubelet Back-off restarting failed container kube-scheduler in pod kube-scheduler-controller_kube-system(533f943efad0a8211a54e7f55baaac1f) Normal Pulled 5m11s (x2 over 6m21s) kubelet Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine Normal Created 5m11s (x2 over 6m17s) kubelet Created container: kube-scheduler Normal Started 5m11s (x2 over 6m17s) kubelet Started container kube-scheduler