Skip to content

Commit

Permalink
Update wcp install doc
Browse files Browse the repository at this point in the history
Signed-off-by: Xing Yang <[email protected]>
  • Loading branch information
xing-yang committed Jan 16, 2025
1 parent 9b56f04 commit b3fc657
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 7 deletions.
Binary file removed docs/how-to-enable-supervisor-service.png
Binary file not shown.
12 changes: 5 additions & 7 deletions docs/velero-vsphere-operator-user-manual.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,13 @@
Users here are expected to be vSphere users with access to:

* vSphere UI
* [Kubectl vSphere plugin](https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-0F6E45C4-3CB1-4562-9370-686668519FCA.html)
* [Kubectl vSphere plugin](https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-tkg/GUID-8699B9DE-01D9-4B2A-BBFB-EB1D81878587.html)

## Installing Velero on Supervisor cluster

1. Enable `Velero vSphere Operator` Supervisor Service via vSphere UI. If you do not see any of the Supervisor Services as shown below, please double check the [compatibility](supervisor.md#compatibility) matrix.
![How to enable `Velero vSphere Operator` supervisor service](how-to-enable-supervisor-service.png)
Note: `Velero vSphere Operator` Supervisor Service is enabled by default on vSphere 80u3 and later.

2. Create a supervisor namespace for Velero instance via vSphere UI.
1. Create a supervisor namespace for Velero instance via vSphere UI.
![How to create a supervisor namespace](how-to-create-supervisor-namespace.png)

And for user doesn't have VI Admin role, please add **EDIT** permission to the Supervisor namespace.
Expand All @@ -19,7 +18,7 @@ Users here are expected to be vSphere users with access to:
Below is an example.
![What to do when adding edit permission](grant-edit-permission.png)

3. Create Velero vSphere Plugin Config
2. Create Velero vSphere Plugin Config

The config map is used to specify that the plugin is being installed on `SUPERVISOR` cluster.

Expand All @@ -33,9 +32,8 @@ data:
cluster_flavor: SUPERVISOR
EOF
```

4. Run [Velero vSphere Operator CLI](velero-vsphere-operator-cli.md), **velero-vsphere**, to install Velero into the same namespace created in step 2 above.
3. Run [Velero vSphere Operator CLI](velero-vsphere-operator-cli.md), **velero-vsphere**, to install Velero into the same namespace created in the previous step.
Assume users have logged in `kubectl vSphere plugin` as vSphere users.
Below are some examples about `velero-vsphere install` for different object stores as backup storage locations of Velero.

Expand Down

0 comments on commit b3fc657

Please sign in to comment.