Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/199.19.213.169 Start Time: Tue, 12 May 2026 11:32:27 +0000 Labels: component=kube-scheduler tier=control-plane Annotations: kubernetes.io/config.hash: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.mirror: 52c03224580ac568b66c5ffba7a99547 kubernetes.io/config.seen: 2026-05-12T11:32:15.002312007Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.19.213.169 IPs: IP: 199.19.213.169 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://d091143f5fd04fcd6bba5f541796c50b4fbad7cc2300e03766a458150e5d60d9 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, 12 May 2026 12:36:44 +0000 Ready: True Restart Count: 4 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 38m (x9 over 49m) kubelet Liveness probe failed: Get "https://199.19.213.169:10259/healthz": dial tcp 199.19.213.169:10259: connect: connection refused Normal Killing 38m kubelet Container kube-scheduler failed liveness probe, will be restarted Warning Failed 34m kubelet Error: stream terminated by RST_STREAM with error code: CANCEL Warning Failed 34m (x3 over 34m) kubelet Error: failed to reserve container name "kube-scheduler_kube-scheduler-instance_kube-system_52c03224580ac568b66c5ffba7a99547_3"; check if another CreateContainer request is in progress: name "kube-scheduler_kube-scheduler-instance_kube-system_52c03224580ac568b66c5ffba7a99547_3" is reserved for "a031e9a71bc74fb7f8231502b75083d672686715c3db6ba0ac3c3c706204d0e7" Normal Pulled 34m (x7 over 79m) kubelet Container image "harbor.atmosphere.dev/registry.k8s.io/kube-scheduler:v1.28.13" already present on machine Normal Created 34m (x3 over 79m) kubelet Created container kube-scheduler Normal Started 34m (x3 over 79m) kubelet Started container kube-scheduler