Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/199.204.45.3 Start Time: Tue, 28 Apr 2026 03:17:46 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.seen: 2026-04-28T03:17:46.582290277Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.204.45.3 IPs: IP: 199.204.45.3 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://ee7b9b8298353bc9a9c6343ab9f4ce09c3e65e6cdeac835538b48b22788fe5c4 Image: harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13 Image ID: harbor.atmosphere.dev/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: Tue, 28 Apr 2026 03:32:34 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Tue, 28 Apr 2026 03:25:39 +0000 Finished: Tue, 28 Apr 2026 03:30:17 +0000 Ready: True Restart Count: 5 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 ---- ------ ---- ---- ------- Warning Unhealthy 48m kubelet Liveness probe failed: Get "https://199.204.45.3:10259/healthz": read tcp 199.204.45.3:45906->199.204.45.3:10259: read: connection reset by peer Normal Started 46m (x3 over 49m) kubelet Started container kube-scheduler Warning Unhealthy 45m kubelet Liveness probe failed: Get "https://199.204.45.3:10259/healthz": read tcp 199.204.45.3:46168->199.204.45.3:10259: read: connection reset by peer Warning BackOff 44m (x11 over 48m) kubelet Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(52c03224580ac568b66c5ffba7a99547) Normal Pulled 44m (x4 over 49m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 44m (x4 over 49m) kubelet Created container kube-scheduler Warning Unhealthy 39m kubelet Liveness probe failed: Get "https://199.204.45.3:10259/healthz": read tcp 199.204.45.3:47816->199.204.45.3:10259: read: connection reset by peer Warning Unhealthy 39m (x2 over 45m) kubelet Liveness probe failed: Get "https://199.204.45.3:10259/healthz": dial tcp 199.204.45.3:10259: connect: connection refused