From 8859766b5d889b914368cf0a1d4666c42546aa97 Mon Sep 17 00:00:00 2001 From: Carlisia Date: Tue, 4 Feb 2020 12:27:47 -0800 Subject: [PATCH] Code reviews Signed-off-by: Carlisia --- site/docs/master/namespace.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/site/docs/master/namespace.md b/site/docs/master/namespace.md index 5f9d06211..9a3d62808 100644 --- a/site/docs/master/namespace.md +++ b/site/docs/master/namespace.md @@ -1,14 +1,14 @@ -# Run in a custom namespace +# Run in a non-default namespace -The Velero installation and backups by default are run in the `velero` namespace. However, it is possible to customize it. +The Velero installation and backups by default are run in the `velero` namespace. However, it is possible to use a different namespace. -### 1) Customize the namespace on the cluster +### 1) Customize the namespace during install -Use the `--namespace` flag, in conjunction with the other flags in the `velero install` command (as shown in the [the Velero install instructions][0]). This will inform Velero where to run. +Use the `--namespace` flag, in conjunction with the other flags in the `velero install` command (as shown in the [the Velero install instructions][0]). This will inform Velero where to install. ### 2) Customize the namespace for operational commands -To have namespace consistency, specify the namespace for all Velero operational commands same as the namespace used to install Velero: +To have namespace consistency, specify the namespace for all Velero operational commands to be the same as the namespace used to install Velero: ```bash velero client config set namespace=