Before you install and configure VMware Cloud Director extension for Data Solutions, verify that you are familiar with the supported product versions and that you have all the necessary privileges to complete specific operations.

Interoperability information

Data solutions support

Solution Kubernetes Component VMware Cloud Director extension for Data Solutions 1.0 VMware Cloud Director extension for Data Solutions 1.1 VMware Cloud Director extension for Data Solutions 1.2 VMware Cloud Director extension for Data Solutions 1.3
VMware RabbitMQ

VMware RabbitMQ for Kubernetes

See VMware RabbitMQ for Kubernetes Documentation

 1.3 1.3, 1.4 1.3, 1.4 1.4, 1.5
VMware SQL with MySQL

VMware SQL with MySQL for Kubernetes

See VMware SQL with MySQL for Kubernetes Documentation

 Not supported 1.5, 1.6 1.7, 1.8 1.9, 1.10
VMware SQL with Postgres

VMware SQL with Postgres for Kubernetes

See VMware SQL with Postgres for Kubernetes Documentation

 Not supported 1.9, 2.0 2.0, 2.1 2.1, 2.2
MongoDB Enterprise

MongoDB Enterprise for Kubernetes

See MongoDB Enterprise Kubernetes Documentation

 Not supported Not supported 1.20 1.22, 1.23
MongoDB Community

MongoDB Community for Kubernetes

See MongoDB Community Kubernetes Documentation

 Not supported Not supported 0.8 0.8.3
Confluent Platform

Confluent Platform for Kubernetes

See Confluent for Kubernetes Documentation

 Not supported Not supported Not supported 2.7.2 with Helm Chart version 0.824.33

External Components

Note:
  • If you want to use a load balancer with TLS for VMware RabbitMQ, you need vSphere Cloud Provider Interface version 1.3.0 or later. You can configure it in VMware Cloud Director Container Service Extension.
  • For VMware Tanzu Kubernetes Grid Multi-Cloud versions 2.1 and 2.1.1, and from VMware Cloud Director Container Service Extension 4.1, Prometheus and Grafana are not installed on the VMware Tanzu Kubernetes Grid cluster. The cluster owner must install Prometheus and Grafana before the installation of VMware Cloud Director extension for Data Solutions. See Installing and Managing Packages with the Tanzu CLI.
Component VMware Cloud Director extension for Data Solutions
VMware Cloud Director Container Service Extension 4.0 and later
Kubernetes 1.22 and later
VMware Tanzu Kubernetes Grid Multi-Cloud 1.6.1, 2.1.1, 2.2.0

For more information on interoperability, see the VMware Product Interoperability Matrix.

Access control and user roles

Ensure that you are familiar with the various user roles in VMware Cloud Director extension for Data Solutions and their respective rights.

Provider administrators install the VMware Cloud Director extension for Data Solutions to VMware Cloud Director and perform various provider operations within the extension.

Tenant administrators can view all the data within their organization. They might have the rights to provision Kubernetes clusters and to create data solution instances.

What roles do you need for VMware Cloud Director extension for Data Solutions?

You must create the following roles:
  • Tenant VMware Cloud Director extension for Data Solutions operator.

    You can clone a role from the global Kubernetes Cluster Author and include the Edit VMWARE:CAPVCDCLUSTER right. The specific user must be given ReadWrite right in the access control list of the cluster Runtime Defined Entity (RDE) instance. You must reassign the cluster owner to the new role before installing the Data Solutions operator to the Tanzu Kubernetes Grid multi-cloud cluster.

    This role is responsible for installing the VMware Cloud Director Data Solutions operator to Tanzu Kubernetes Grid multi-cloud. In addition to the required rights for this role, the tenant operators must also have edit right on specific Tanzu Kubernetes Grid multi-cloud clusters.

  • Tenant VMware Cloud Director extension for Data Solutions user

    The users must be given the role or the equivalent rights to create data instances.

    The users in this role perform day-to-day operations on the data solution instance management, for example, creation, update, and deletion.

User roles and rights reference

VMware Cloud Director extension for Data Solutions role Description VMware Cloud Director roles and rights
Provider administrator You need this role to:
  • Install and onboard VMware Cloud Director extension for Data Solutions.
  • Publish VMware Cloud Director extension for Data Solutions to tenant organizations.
  • Manage container registries.
  • Manage solution templates.
  • View VMware Cloud Director extension for Data Solutions usage metrics.
 Provider administrator
Tenant administrator You need this role to:
  • View published data solutions.
  • View data solution instances.
  • View the Tanzu Kubernetes Grid multi-cloud activation status.
  • View VMware Cloud Director extension for Data Solutions usage metrics.
  • Attach and detach MongoDB Ops Manager to tenant organization.
 Organization administrator
  • Administrator View
  • View Tenant Portal Plugin Information
  • Administrator View: VMWARE:CAPVCDCLUSTER
  • Administrator View: VMWARE:DSCONFIG
  • Administrator View: VMWARE:DSINSTANCETEMPLATE
  • Administrator View: VMWARE:DSINSTANCE
  • Administrator View: VMWARE:DSPROVISIONING
  • Administrator View: VMWARE:DSCLUSTER
  • View: VMWARE:DSORGCONFIG
  • Full Control: VMWARE:DSORGCONFIG
Tenant VMware Cloud Director extension for Data Solutions operator You need this role to:

Activate Tanzu Kubernetes Grid multi-cloud for VMware Cloud Director extension for Data Solutions.

 Custom VMware Cloud Director role
  • Administrator View
  • View Tenant Portal Plugin Information
  • View: VMWARE:CAPVCDCLUSTER
  • View: VMWARE:DSCONFIG
  • View: VMWARE:DSPROVISIONING
  • View: VMWARE:DSINSTANCE
  • View: VMWARE:DSINSTANCETEMPLATE
  • View: VMWARE:DSCLUSTER
  • Manage user's own API token
  • Edit: VMWARE:CAPVCDCLUSTER
  • Full Control: VMWARE:DSPROVISIONING
  • Full Control: VMWARE:DSCLUSTER
  • Administrator Full Control: VMWARE:DSINSTANCE
  • Full Control: VMWARE:DSORGCONFIG
  • View: VMWARE:DSORGCONFIG
Tenant VMware Cloud Director extension for Data Solutions user You need this role to:
  • View published data solutions.
  • Manage data solution instances.
 Custom VMware Cloud Director role
  • View Tenant Portal Plugin Information
  • View: VMWARE:CAPVCDCLUSTER
  • View: VMWARE:DSCONFIG
  • View: VMWARE:DSPROVISIONING
  • View: VMWARE:DSINSTANCE
  • View: VMWARE:DSINSTANCETEMPLATE
  • View: VMWARE:DSCLUSTER
  • View: VMWARE:DSORGCONFIG
  • Full Control: VMWARE:DSINSTANCE

Network ports configuration

Ensure that the required network ports are open for the VMware Cloud Director extension for Data Solutions data solutions communication.

Table 1. Ports and protocols required for VMware Cloud Director extension for Data Solutions
Source Destination Port Protocol Data Solution Description
Tenant Kubernetes cluster DNS Server 53 TCP MongoDB Used when MongoDB Enterprise ReplicaSet enables the LoadBalancer service.
Tenant Kubernetes cluster VMware Cloud Director Server 443 TCP All Used for communication between the tenant Kubernetes cluster and the VMware Cloud Director server.
Tenant Kubernetes cluster VMware Harbor Registry 443 TCP All Used when the tenant Kubernetes cluster pulls VMware Cloud Director Data Solutions operator images.
Tenant Kubernetes cluster VMware Harbor Registry 443 TCP RabbitMQ, MySQL, Postgres Used when the tenant Kubernetes cluster pulls VMware Data Solutions images.
Tenant Kubernetes cluster MongoDB helm chart repository 443 TCP MongoDB Used when the tenant Kubernetes cluster pulls MongoDB Enterprise or MongoDB Community helm charts.
Tenant Kubernetes cluster Docker Hub 443 TCP MongoDB Used when MongoDB Enterprise or MongoDB Community pulls images from the Docker Hub.
Tenant Kubernetes cluster MongoDB Official Docker Hub 443 TCP MongoDB Used when MongoDB Enterprise or MongoDB Community pulls images from the MongoDB Official Docker Hub.
Web Browser Tenant Kubernetes cluster 443 TCP All Used when the user accesses the Grafana Dashboard for data service monitoring.
MySQL Client Tenant Kubernetes cluster 3306 TCP MySQL Used for MySQL clients to connect to the MySQL server.
Postgres Client Tenant Kubernetes cluster 5432 TCP Postgres Used for Postgres clients to connect to the Postgres server.
RabbitMQ Client Tenant Kubernetes cluster 5672 TCP RabbitMQ Used for RabbitMQ clients to connect to the RabbitMQ server.
Web Browser Tenant Kubernetes cluster 15672 TCP RabbitMQ Used when the user accesses the RabbitMQ Management Console.
MongoDB Client Tenant Kubernetes cluster 27017 TCP MongoDB Used for MongoDB clients to connect to the MongoDB server.
Tenant Kubernetes cluster MongoDB Ops Manager 80/443 TCP MongoDB Used for communication between the tenant Kubernetes cluster and the MongoDB Ops Manager.
Kafka client Tenant Kubernetes cluster 9092 TCP Confluent Platform Used for Kafka clients to connect to the Kafka server.