Name: kube-scheduler-controller Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: controller/199.19.213.31 Start Time: Wed, 22 Apr 2026 09:32:04 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 533f943efad0a8211a54e7f55baaac1f kubernetes.io/config.mirror: 533f943efad0a8211a54e7f55baaac1f kubernetes.io/config.seen: 2026-04-22T09:31:52.364821531Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.19.213.31 IPs: IP: 199.19.213.31 Controlled By: Node/controller Containers: kube-scheduler: Container ID: containerd://2d3db918f4913a73b9491d17393e8e84c44b8c6d59746f338418aea07b4f8f21 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: Wed, 22 Apr 2026 09:33:12 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Wed, 22 Apr 2026 09:31:56 +0000 Finished: Wed, 22 Apr 2026 09:33:08 +0000 Ready: True Restart Count: 1 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 113s kubelet Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine Normal Created 113s kubelet Created container: kube-scheduler Normal Started 113s kubelet Started container kube-scheduler Warning Unhealthy 102s (x5 over 104s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500 Warning Unhealthy 41s kubelet Readiness probe failed: Get "https://199.19.213.31:10259/readyz": dial tcp 199.19.213.31:10259: connect: connection refused Normal Pulled 40s kubelet Container image "registry.k8s.io/kube-scheduler:v1.34.0" already present on machine Normal Created 38s kubelet Created container: kube-scheduler Normal Started 37s kubelet Started container kube-scheduler