Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/162.253.55.110 Start Time: Fri, 20 Feb 2026 18:27:25 +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-20T18:27:19.074432502Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 162.253.55.110 IPs: IP: 162.253.55.110 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://249d016de9395f2c876d0e4bec288be67fc657a0200d6b1a903e04f3b7c372d8 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: Fri, 20 Feb 2026 18:32:26 +0000 Last State: Terminated Reason: Error Exit Code: 1 Started: Fri, 20 Feb 2026 18:27:19 +0000 Finished: Fri, 20 Feb 2026 18:30:12 +0000 Ready: True Restart Count: 1 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 9m32s kubelet Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 9m32s kubelet Created container kube-scheduler Normal Started 9m32s kubelet Started container kube-scheduler Warning Unhealthy 5m20s (x8 over 6m30s) kubelet Liveness probe failed: Get "https://162.253.55.110:10259/healthz": dial tcp 162.253.55.110:10259: connect: connection refused Normal Killing 5m20s kubelet Container kube-scheduler failed liveness probe, will be restarted Normal Pulled 4m26s kubelet Container image "registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 4m25s kubelet Created container kube-scheduler Normal Started 4m25s kubelet Started container kube-scheduler