vSphere with Tanzu integrates with several third-party application services that include object storage, non-relational databases, and so on. As a vSphere administrator, enable the services available onvCenter Server.

In vSphere with Tanzu 7.0 Update 1 and later, all available third-party services ship inside the supervisor services platform. YAML files that describe the services are stored in the locally available repository. When you enable a service, the platform uses an appropriate YAML file to deploy the service in the corresponding namespace.

After you enable the service, the vSAN Data Persistence platform performs the following actions to create necessary resources for the service:
  • Creates a namespace for this service in the supervisor cluster.
  • Creates storage policies to be used with vSAN Shared-Nothing-Architecture (SNA) and vSAN Direct datastores. In vSphere 7.0 Update 2, the vSAN Direct storage policy is capability-based. If you created tag-based policies in vSphere 7.0 Update 1, they are automatically converted to capability-based after an upgrade to vSphere 7.0 Update 2.
  • Creates two DevOps roles, one with edit permissions and another with view permissions.

    When the service operator is displayed, its custom CRDs are installed in the Supervisor Cluster. Users with the edit permission can CRUD resources of these CRDs in the namespace they have permission for. Users with the view permission can only view resources of this CRD.

  • If the third party has provided a custom UI plugin, it appears in the vSphere Client. The vSphere administrator can use the plugin to manage the service. For more information, see the third-party UI plugin documentation.


If you use a private repository to store certified images of the application services, follow third-party guidelines to push the images to the repository.


  1. In the vSphere Client, navigate to the host cluster that has Workload Management enabled.
  2. Click the Configure tab and click Services under Supervisor Services.
    You can see all services available on vCenter Server.
  3. Select a service, such as MinIO, and click Enable.
  4. If you use a private repository for the services images, provide parameters to access the repository.
    The parameters might include the location of a locally available YAML that describes the service, username and password, and advanced settings.
    For security reasons, the values you provide will not be available for reviewing or editing later in the vSphere Client.
  5. Accept the license agreement and click Finish.
  6. Select the namespace created for the service and click the Summary tab to verify that all appropriate resources for the service have been created.
    The Summary page shows storage policies assigned to the namespace, the vSphere Pods running on the namespace, and so on.

What to do next

If you want to create new storage policies and assign them to the service namespace, see Create vSAN Direct Storage Policy and Create vSAN SNA Storage Policy.