From 2fb8128b302c686e5d573ed57e92e0d4e36a88bb Mon Sep 17 00:00:00 2001 From: Rajesh Deshpande Date: Mon, 24 Jun 2019 12:03:55 +0530 Subject: [PATCH] Correcting details about current request namespace (#15061) Removed ambiguous word 'temporarily', as namespace set using that method, is not temporary. It is permanent for a current resource and there is no concept of a temporary namespace in K8s. Also, for consisteny '--namespace' flag added after the actual command. --- .../concepts/overview/working-with-objects/namespaces.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/overview/working-with-objects/namespaces.md b/content/en/docs/concepts/overview/working-with-objects/namespaces.md index a6accb8696..539ad212ca 100644 --- a/content/en/docs/concepts/overview/working-with-objects/namespaces.md +++ b/content/en/docs/concepts/overview/working-with-objects/namespaces.md @@ -65,13 +65,13 @@ Kubernetes starts with three initial namespaces: ### Setting the namespace for a request -To temporarily set the namespace for a request, use the `--namespace` flag. +To set the namespace for a current request, use the `--namespace` flag. For example: ```shell -kubectl --namespace= run nginx --image=nginx -kubectl --namespace= get pods +kubectl run nginx --image=nginx --namespace= +kubectl get pods --namespace= ``` ### Setting the namespace preference