Install a Supervisor Service on Supervisor Clusters

After adding a Supervisor Service to vCenter Server, you can install it on Supervisor Clusters in your vSphere with Tanzu environment. If you install a newer version of a Supervisor Service, it overrides any older service versions on that Supervisor Cluster. Only one version of a Supervisor Service can run on a Supervisor Cluster at a time.

• Learn more about the supported Supervisor Services and how to download their service YAML files at http://vmware.com/go/supervisor-service.

Prerequisites

• Add a new Supervisor Service or a newer version of and existing service to vCenter Server. See Add a Supervisor Service to vCenter Server or Add a New Version to a Supervisor Service.

• Verify that you have the Manage Supervisor Services privilege on the vCenter Server system that hosts the Supervisor Cluster where you install the service.

• If the Supervisor Service requires persistent storage, configure the vSAN Data Persistence platform. See Using vSAN Data Persistence Platform with Modern Stateful Services.

Procedure

1. From the vSphere Client home menu, select Workload Management.
2. Select Services.
3. Select the Supervisor Service version that you want to install.
   Note:

   You cannot install Supervisor Service versions that are Deactivated.

4. Select the Supervisor Cluster where you want to install the service.
5. Fill in the registry endpoint, user name, and password if you have hosted the images in a private registry.

   Other key-value pairs might exist in case the service requires them. Refer to the service documentation for more details.

Results

The Supervisor Service is in Configuring state, which means that all the necessary resources are being created in the Supervisor Cluster and the service YAML is being applied to the cluster. Once the YAML is successfully applied to the Supervisor Cluster with all its resources and namespace created or updated, the service state changes to Configured. The service is available to all the namespaces in that cluster and DevOps engineers can use it with their Kubernetes workloads.

Note:

The Supervisor Cluster is not monitoring if the Supervisor Service is actually working. For example, if you have specified incorrect registry user name or password, the service might not be able to fetch any of the images that it needs to run. This way, the service might show as Configured but it's not actually working. To confirm if the Supervisor Service is working or not, check the service namespace and the running pods.

What to do next

Configure the Supervisor Service by using the interface. See where to find it at Access the Management Interface of a Supervisor Service on the Supervisor Cluster.