Name: kube-scheduler-instance Namespace: kube-system Priority: 2000001000 Priority Class Name: system-node-critical Node: instance/199.19.213.114 Start Time: Thu, 02 Apr 2026 06:06:03 +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-02T06:05:56.306065514Z kubernetes.io/config.source: file Status: Running SeccompProfile: RuntimeDefault IP: 199.19.213.114 IPs: IP: 199.19.213.114 Controlled By: Node/instance Containers: kube-scheduler: Container ID: containerd://30261b3cb5e0d8ea47089145832b0434d277765c4fd321115757c47211934beb 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, 02 Apr 2026 06:05:57 +0000 Ready: True Restart Count: 0 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: