If you are deploying App Launchpad to a VMware Cloud Director service environment, make sure that your VMware Cloud Director service instance meets the following requirements.
- You need a provider account for VMware Cloud Director service that is assigned with the System Administrator role or an account with a permission equivalent role. You use this account to complete the configuration of App Launchpad.
- Create a provider virtual data center (VDC) and a network pool in an SDDC. You use the resources to create a virtual machine that is dedicated for App Launchpad services.
- Deploy a CentOS or Red Hat Enterprise Linux virtual machine to your provider virtual data center. You use the virtual machine as a target for deploying App Launchpad.
- Use the user interface of vCenter Server to create a connection between App Launchpad and a network that is backed by the Compute Gateway(CGW). Make sure that the virtual machine has access to all tier-1 edge gateways of the tenant organizations where the Kubernetes clusters are deployed.
- Configure a gateway firewall rule that allows access from App Launchpad to external networks. The virtual machine to which you deploy App Launchpad does not require inbound access and requires a limited outbound access to the following destinations:
- The VMware Cloud Director service instance on AWS
- VMware Cloud Services
- VMware Marketplace
- VMware Analytics Cloud
- If your customers plan to deploy container applications to a tenant organization, configure external addresses for the Kubernetes clusters in the tenant organization. Make sure that the external addresses of the Kubernetes clusters on the tier-1 edge gateway are known and accessible for App Launchpad. See https://kb.vmware.com/s/article/83215.
For more information about VMware Cloud Director service, see https://docs.vmware.com/en/VMware-Cloud-Director-service/index.html.
For more information about VMware Cloud on AWS, see https://docs.vmware.com/en/VMware-Cloud-on-AWS/index.html.
