Before you begin
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
The interoperability information defines the qualified products and software versions you can use with
VMware Cloud Director extension for Data Solutions
.Data solutions support
Solution |
Kubernetes Component |
VMware Cloud Director extension for Data Solutions 1.3 |
VMware Cloud Director extension for Data Solutions 1.4 |
VMware Cloud Director extension for Data Solutions 1.5 |
---|---|---|---|---|
VMware RabbitMQ
|
VMware RabbitMQ for Kubernetes See VMware RabbitMQ for Kubernetes Documentation |
1.4, 1.5 |
1.4, 1.5 |
1.4, 1.5 |
VMware SQL with MySQL
|
VMware SQL with MySQL for Kubernetes See VMware SQL with MySQL for Kubernetes Documentation |
1.9, 1.10 |
1.9, 1.10 |
1.9, 1.10 |
VMware SQL with Postgres
|
VMware SQL with Postgres for Kubernetes See VMware SQL with Postgres for Kubernetes Documentation |
2.1, 2.2 |
2.2, 2.3 |
2.2, 2.3 |
MongoDB Enterprise
|
MongoDB Enterprise for Kubernetes |
1.22, 1.23 |
1.23, 1.24 |
1.23, 1.24 |
MongoDB Community
|
MongoDB Community for Kubernetes |
0.8.3 |
0.9.0 |
0.9.0 |
Confluent Platform
|
Confluent Platform for Kubernetes |
2.7.2 with Helm Chart version 0.824.33 |
2.7.3 with Helm Chart version 0.824.40 |
2.7.3 with Helm Chart version 0.824.40 |
VMware Data Services Manager MySQL
|
See VMware Data Services Manager Documentation |
Not supported |
Not supported |
2.1.0 |
VMware Data Services Manager Postgres
|
See VMware Data Services Manager Documentation |
Not supported |
Not supported |
2.1.0 |
External Components
- If you want to use a load balancer with TLS forVMware RabbitMQ, you needvSphere Cloud Provider Interfaceversion 1.3.0 or later. You can configure it inVMware Cloud Director Container Service Extension.
- ForVMware Tanzu Kubernetes GridMulti-Cloud version 2.1.1, and fromVMware Cloud Director Container Service Extension4.1,PrometheusandGrafanaare not installed on theVMware Tanzu Kubernetes Gridcluster. The cluster owner must installPrometheusandGrafanabefore the installation ofVMware Cloud Director extension for Data Solutions. SeeInstalling and Managing Packages with the Tanzu CLIin theVMware Tanzu Kubernetes Grid documentation.
Component |
VMware Cloud Director extension for Data Solutions
|
---|---|
VMware Cloud Director Container Service Extension
|
4.1.1, 4.2.2 |
Kubernetes
|
1.26 and later |
VMware Tanzu Kubernetes Grid Multi-Cloud |
2.1.1, 2.2.0, 2.3.1, 2.4.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?
VMware Cloud Director extension for Data Solutions
?You must create the following roles:
- TenantVMware Cloud Director extension for Data Solutionsoperator.You can clone a role from the globalKubernetes Cluster Authorand include theEdit VMWARE:CAPVCDCLUSTERright. The specific user must be givenReadWriteright 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 theData Solutions operatorto theTanzu Kubernetes Gridmulti-cloud cluster.This role is responsible for installing theVMware Cloud Director Data Solutions operatortoTanzu Kubernetes Gridmulti-cloud. In addition to the required rights for this role, the tenant operators must also have edit right on specificTanzu Kubernetes Gridmulti-cloud clusters.
- TenantVMware Cloud Director extension for Data SolutionsuserThe 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.After upgradingVMware Cloud Director extension for Data Solutionsto version 1.5 you must manually update theTenant VMware Cloud Director extension for Data Solutions operatorandTenant VMware Cloud Director extension for Data Solutions userroles with theVMware Cloud Director extension for Data Solutions1.5 rights.
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:
|
Provider administrator
|
Tenant administrator
|
You need this role to:
|
Organization administrator
|
Tenant VMware Cloud Director extension for Data Solutions operator
|
You need this role to: Install, update, and
uninstall the Data Solutions operator for VMware Cloud Director extension for Data Solutions . |
Custom VMware Cloud Director rights
VMware Cloud Director extension for Data Solutions 1.5
rights:
|
Tenant VMware Cloud Director extension for Data Solutions user
|
You need this role to:
|
Custom VMware Cloud Director rights
VMware Cloud Director extension for Data Solutions 1.5
rights:
|
Network ports configuration
Ensure
that the required network ports are open for the
VMware Cloud Director extension for Data Solutions
data solutions communication.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. |
Provider Kubernetes
cluster |
VMware Data Services Manager server |
443 |
TCP |
VMware Data Services Manager
|
Used by the VMware Data Services Manager consumption operator to access the
VMware Data Services Manager server. |
Provider Kubernetes
cluster |
Broadcom registry |
443 |
TCP |
VMware Data Services Manager
|
Used by Kubelet to pull VMware Cloud Director extension for Data Solutions and VMware Data Services Manager
consumption operator images. |
MySQL client |
vSphere workload
network |
3306 |
TCP |
VMware Data Services Manager MySQL
|
Used by MySQL clients
to access the MySQL
server. |
Postgres
client |
vSphere workload
network |
5432 |
TCP |
VMware Data Services Manager Postgres
|
Used by Postgres
clients to access the Postgres server. |