Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/199.19.213.196 Start Time: Thu, 06 Aug 2026 07:04:01 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.seen: 2026-08-06T07:04:01.092311824Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.19.213.196 IPs: IP: 199.19.213.196 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://0c746f37597cdc7092ec150922e081135bab975ab8d3ab4ad5328a76e966c629 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: Thu, 06 Aug 2026 07:11:25 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Thu, 06 Aug 2026 07:09:23 +0000 Finished: Thu, 06 Aug 2026 07:11:03 +0000 Ready: True Restart Count: 3 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 3m4s kubelet Liveness probe failed: Get "https://199.19.213.196:10259/healthz": read tcp 199.19.213.196:41504->199.19.213.196:10259: read: connection reset by peer Warning Unhealthy 75s kubelet Liveness probe failed: Get "https://199.19.213.196:10259/healthz": net/http: TLS handshake timeout Warning Unhealthy 73s kubelet Liveness probe failed: Get "https://199.19.213.196:10259/healthz": read tcp 199.19.213.196:38430->199.19.213.196:10259: read: connection reset by peer Warning Unhealthy 61s (x2 over 71s) kubelet Liveness probe failed: Get "https://199.19.213.196:10259/healthz": dial tcp 199.19.213.196:10259: connect: connection refused Warning BackOff 53s (x4 over 3m2s) kubelet Back-off restarting failed container kube-scheduler in pod kube-scheduler-instance_kube-system(52c03224580ac568b66c5ffba7a99547) Normal Pulled 51s (x3 over 3m59s) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 51s (x3 over 3m58s) kubelet Created container kube-scheduler Normal Started 51s (x3 over 3m58s) kubelet Started container kube-scheduler