Before you can install , and use VMware Cloud Director Extension for VMware Tanzu Mission Control, it is necessary to prepare your environment so it is compatible.
Ensure the following components are in place for
VMware Cloud Director Extension for VMware Tanzu Mission Control to operate successfully.
- Install VMware Cloud Director 10.5.1. For more information, see VMware Cloud Director Installation, Configuration, and Upgrade Guide.
- Install VMware Cloud Director Container Service Extension 4.2, and Kubernetes Container Clusters 4.2 UI plugin. For more information, see Installing, Configuring, and Upgrading VMware Cloud Director Container Service Extension as a Service Provider.
- Configure a Solution Organization. This is used to configure the Solution Add-On Landing Zone. This is usually the same organization that is used to host the VMware Cloud Director Container Service Extension server. For more information, see Create an Organization.
- Configure a Tenant Organization. For more information, see Create an Organization.
Deploy a Harbor registry to host the VMware Cloud Director Extension for VMware Tanzu Mission Control images.
- Configure the Solution Add-On Landing Zone. For more information, see Configure Your Solution Add-On Landing Zone.
- Install VMware Cloud Director® Object Storage Extension™ to back up the cluster that hosts VMware Cloud Director Extension for VMware Tanzu Mission Control. For more information, see Installing, Configuring, and Upgrading VMware Cloud Director Object Storage Extension.
- Configure DNS records for the DNS zone to the external IP of VMware Cloud Director Extension for VMware Tanzu Mission Control, for example,
tmc.mycloud.local → 10.100.1.2. It is necessary to map the following subdomains to the same external IP:Sub domains <tmc_zone>alertmanager.<tmc_zone>auth.<tmc_zone>blob.<tmc_zone>gts.<tmc_zone>gts-rest.<tmc_zone>landing.<tmc_zone>pinniped-supervisor.<tmc_zone>prometheus.<tmc_zone>grafana.<tmc_zone>s3.<tmc_zone>console.s3.<tmc_zone>tmc-local.s3.<tmc_zone>
