From 0e70ff0230219e711bd241ed6e737ab990d6afd6 Mon Sep 17 00:00:00 2001 From: Wei Huang Date: Fri, 18 Nov 2022 10:43:45 -0800 Subject: [PATCH] fixup: address comments --- .../scheduling-eviction/pod-scheduling-readiness.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md index fd3f27f42f360..b8a9dd69e19b0 100644 --- a/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md +++ b/content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md @@ -57,7 +57,7 @@ kubectl get pod test-pod The output reveals it's in `SchedulingGated` state: -```bash +```none NAME READY STATUS RESTARTS AGE test-pod 0/1 SchedulingGated 0 7s ``` @@ -70,7 +70,7 @@ kubectl get pod test-pod -o jsonpath='{.spec.schedulingGates}' The output is: -```bash +```none [{"name":"foo"},{"name":"bar"}] ``` @@ -94,7 +94,7 @@ kubectl get pod test-pod -o wide Given the test-pod doesn't request any CPU/memory resources, it's expected that this Pod's state get transited from previous `SchedulingGated` to `Running`: -```bash +```none NAME READY STATUS RESTARTS AGE IP NODE test-pod 1/1 Running 0 15s 10.0.0.4 node-2 ```