You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
11
-

10
+
Note: `Velero vSphere Operator` Supervisor Service is enabled by default on vSphere 80u3 and later.
12
11
13
-
2. Create a supervisor namespace for Velero instance via vSphere UI.
12
+
1. Create a supervisor namespace for Velero instance via vSphere UI.
14
13

15
14
16
15
And for user doesn't have VI Admin role, please add **EDIT** permission to the Supervisor namespace.
@@ -19,7 +18,7 @@ Users here are expected to be vSphere users with access to:
19
18
Below is an example.
20
19

21
20
22
-
3. Create Velero vSphere Plugin Config
21
+
2. Create Velero vSphere Plugin Config
23
22
24
23
The config map is used to specify that the plugin is being installed on `SUPERVISOR` cluster.
25
24
@@ -33,9 +32,8 @@ data:
33
32
cluster_flavor: SUPERVISOR
34
33
EOF
35
34
```
36
-
37
35
38
-
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.
36
+
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.
39
37
Assume users have logged in `kubectl vSphere plugin` as vSphere users.
40
38
Below are some examples about `velero-vsphere install` for different object stores as backup storage locations of Velero.
0 commit comments