Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/199.204.45.227 Start Time: Wed, 04 Feb 2026 10:59:36 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 4cec6c3159d80558328947d0819d07fb kubernetes.io/config.mirror: 4cec6c3159d80558328947d0819d07fb kubernetes.io/config.seen: 2026-02-04T10:59:29.330211882Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.204.45.227 IPs: IP: 199.204.45.227 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://8909ab7412d01e094d984d73dfd0af78bbd368a60410ed718d002b80df657e4e Image: registry.k8s.io/kube-scheduler:v1.28.13 Image ID: registry.k8s.io/kube-scheduler@sha256:efeb791718f4b9c62bd683f5b403da520f3651cb36ad9f800e0f98b595beafa4 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: Wed, 04 Feb 2026 11:02:20 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Wed, 04 Feb 2026 11:01:32 +0000 Finished: Wed, 04 Feb 2026 11:01:58 +0000 Ready: True Restart Count: 2 Requests: cpu: 100m Liveness: http-get https://:10259/healthz delay=10s timeout=15s period=10s #success=1 #failure=8 Startup: http-get https://:10259/healthz delay=10s timeout=15s period=10s #success=1 #failure=24 Environment: Mounts: /etc/kubernetes/scheduler.conf from kubeconfig (ro) Conditions: Type Status 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 6m4s kubelet Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 6m4s kubelet Created container kube-scheduler Normal Started 6m4s kubelet Started container kube-scheduler Warning Unhealthy 4m10s kubelet Liveness probe failed: Get "https://199.204.45.227:10259/healthz": dial tcp 199.204.45.227:10259: connect: connection refused Warning BackOff 3m29s (x3 over 3m33s) kubelet Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(4cec6c3159d80558328947d0819d07fb) Normal Pulled 3m14s (x2 over 4m9s) kubelet Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 3m14s (x2 over 4m3s) kubelet Created container kube-scheduler Normal Started 3m14s (x2 over 4m2s) kubelet Started container kube-scheduler