mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-09-30 03:36:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Code reviews

Browse Source 
Signed-off-by: Carlisia <carlisia@vmware.com>
This commit is contained in:
Carlisia
2020-02-04 12:27:47 -08:00
parent ec7c04df2c
commit 8859766b5d
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
site/docs/master/namespace.md
+5 -5
View File
@@ -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=<NAMESPACE_VALUE>