From 081c7a713c8e7edf2b13e3b06b4f3644b0b7b9f7 Mon Sep 17 00:00:00 2001 From: Sylvain COULOMBEL Date: Sat, 16 May 2020 16:01:39 +0200 Subject: [PATCH] Clean-up extra line in tasks: configure pod container --- .../docs/tasks/configure-pod-container/assign-cpu-resource.md | 3 --- content/en/examples/pods/security/security-context-3.yaml | 3 --- 2 files changed, 6 deletions(-) diff --git a/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md b/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md index a622eb5917..181b92b8e1 100644 --- a/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md +++ b/content/en/docs/tasks/configure-pod-container/assign-cpu-resource.md @@ -180,9 +180,6 @@ The output shows that the Pod status is Pending. That is, the Pod has not been scheduled to run on any Node, and it will remain in the Pending state indefinitely: -```shell -kubectl get pod cpu-demo-2 --namespace=cpu-example -``` ``` NAME READY STATUS RESTARTS AGE cpu-demo-2 0/1 Pending 0 7m diff --git a/content/en/examples/pods/security/security-context-3.yaml b/content/en/examples/pods/security/security-context-3.yaml index 05295e1a03..d68b2a783e 100644 --- a/content/en/examples/pods/security/security-context-3.yaml +++ b/content/en/examples/pods/security/security-context-3.yaml @@ -6,6 +6,3 @@ spec: containers: - name: sec-ctx-3 image: gcr.io/google-samples/node-hello:1.0 - - -