From 6eda6dbc4c80993978bb8bb30b809a1822976fed Mon Sep 17 00:00:00 2001 From: SUNNY Date: Mon, 25 Jun 2018 14:29:02 +0530 Subject: [PATCH] shell command missing fix in docs (#9213) https://kubernetes.io/docs/concepts/overview/object-management-kubectl/imperative-config/#migrating-from-imperative-commands-to-imperative-object-configuration : kubectl shell command broken fix by wrapping kubecl-cmd around codeblock. Added two lines at bottom - Reviewer suggestion --- .../object-management-kubectl/imperative-config.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md b/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md index 7a44a27fc5..f0681fd9b6 100644 --- a/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md +++ b/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md @@ -100,14 +100,16 @@ Migrating from imperative commands to imperative object configuration involves several manual steps. 1. Export the live object to a local object configuration file: - - kubectl get / -o yaml --export > _.yaml +```sh +kubectl get / -o yaml --export > _.yaml +``` 1. Manually remove the status field from the object configuration file. 1. For subsequent object management, use `replace` exclusively. - - kubectl replace -f _.yaml +```sh +kubectl replace -f _.yaml +``` ## Defining controller selectors and PodTemplate labels