Use Tanzu Mission Control to install Tanzu Application Platform (commonly called TAP) on multiple managed clusters.

Prerequisites

Log in to the Tanzu Mission Control console.

Make sure you have the appropriate permissions.
  • To install Tanzu Application Platform (TAP) on a cluster, you must be associated with the cluster.edit role.

Make sure your configuration meets the TAP system requirements specified in Prerequisites for installing Tanzu Application Platform in the VMware Tanzu Application Platform Documentation.

Note:
  • If you have already enabled continuous delivery (CD) or Helm for a cluster, the latest verified version of FluxCD is deployed to the cluster. Because TAP uses an earlier version of FluxCD, and is therefore incompatible with the deployed version, you must first disable CD/Helm on the cluster before attempting to install TAP. If you attempt to install TAP on a cluster where CD/Helm is already enabled, you see an error that looks something like this:
    Solution cannot be installed due to incompatible Continuous Delivery feature components on cluster(s)

    This applies to individual clusters on which you enable CD or Helm, as well as clusters that belong to a cluster group on which you enable CD or Helm. Therefore, if you have enabled CD/Helm for a cluster group that contains one or more clusters on which you want to install TAP, then you must disable CD/Helm for the cluster group before attempting to install TAP on clusters in that cluster group.

    In addition to disabling CD/Helm, you must make sure that the FluxCD package install resources are removed from all clusters, as described in Disable Continuous Delivery.

    If you install TAP prior to enabling CD/Helm, TMC uses the version of FluxCD installed by TAP.

  • Tanzu Mission Control does not deploy TAP on the cluster if TAP packages are already present on the cluster. If you deploy TAP on a cluster through Tanzu Mission Control and then subsequently detach and re-attach the cluster, you must manually remove TAP packages on the cluster before installing TAP again from the Tanzu Mission Control console.
  • There is a known issue related to Tanzu Application Platform TAP-GUI version 1.7.7/1.7.6 where installation fails on Openshift as part of the View profile.
  • There is a known issue that when installing Tanzu Application Platform version 1.7.1 using Tanzu Mission Control on a multi-cluster environment, TAP does not receive ingress location values (secrets with authentication and CA data, and the ingress URL).

    Use the Tanzu Mission Control console to update the build cluster configuration to point to the synced secrets and endpoint location found in the namespace `metadata-store-secrets`.

    grype: 
  metadataStore: 
    authSecret: 
      importFromNamespace: metadata-store-secrets
      name: store-auth-token
    caSecret: 
       importFromNamespace: metadata-store-secrets
       name: store-ca-cert
    url: https://metadata-store.<user-supplied-domain-for-view-cluster>

Procedure

  1. In the Tanzu Mission Control console, click Catalog in the left navigation pane.
  2. Click on the Solutions tab, and then click on Install Tanzu Application Platform selector.
  3. Click the Multi-Cluster tile, and then click the Install Tanzu Application Platform button.
  4. Enter a name for your TAP deployment.
    You can optionally provide a description.
  5. Click Next.
  6. Select the version of TAP that you want to install on the clusters.
  7. Select and configure the View profile, click on the Profile View.
    1. Click to expand the View profile configuration options.
    2. Click Select Cluster to select the cluster on which you want to install TAP with the View profile.
    3. Specify the Ingress domain.
      To access the Tanzu Developer Portal and deployed workloads using a public URL, you must specify an ingress domain. You should create the DNS record after completing the TAP installation.
    4. Enter your entitlement account number.
      The entitlement account number (EAN) is a unique identifier that VMware assigns to customers.
    5. You can optionally enable guest login.
  8. Select and configure the Run profile.
    1. Click Select Cluster to select the cluster on which to install TAP with the Run profile.
    2. Specify the Ingress domain. To access the Tanzu Developer Portal and deployed workloads using a public URL, you must specify an ingress domain. You should create the DNS record after completing the TAP installation.
    3. Optionally you can expand the Configure the Git repository section and change the default settings.
    4. Enter your entitlement account number.
      The entitlement account number (EAN) is a unique identifier that VMware assigns to customers.
    5. The Cluster URL is populated when you select the cluster. You can change it if needed.
    6. The CA certificate is populated when you select the cluster. You can change it if needed.
  9. Select and configure the Build profile.
    1. Click Select Cluster to select the cluster on which to install TAP with the Build profile.
    2. Specify the name of the Supply chain.
      For more information about supply chains, see Overview of Supply Chain Choreographer for Tanzu in the VMware Tanzu Application Platform Documentation.
    3. Specify the parameters for the Image registry provider, including the secret name, the project path, and the secret namespace. These credentials are for pushing and pulling application images.
      You can click Create Secret to configure a new password and new registry configuration.
    4. Select the Namespace provisioner, either Controller or GitOps, and then configure the parameters for the selected provisioner.
      For more information about Namespace provisioner, see Overview of Namespace Provisioner in the VMware Tanzu Application Platform Documentation.
    5. Enter your entitlement account number.
      The entitlement account number (EAN) is a unique identifier that VMware assigns to customers.
    6. You can optionally expand the Configure the Git repository section and change the default settings.
    7. The Cluster URL is populated when you select the cluster. You can change it if needed.
    8. The CA certificate is populated when you select the cluster. You can change it if needed.
    9. You can optionally expand the Advanced Configuration section of the page to configure parameters in the configuration form or YAML.
      Note: To install the Build profile with all build dependencies, add the following section to the YAML configuration. 
      buildservice:
  exclude_dependencies: true
  10. Select and configure the Iterate profile.
    1. Click Select Cluster to select the cluster on which to install TAP with the Iterate profile.
    2. Specify the ingress domain.
      To access the Tanzu Developer Portal and deployed workloads using a public URL, you must specify an ingress domain. Create the DNS record after completing the TAP installation.
    3. Specify the name of the supply chain.
      For more information about supply chains, see Overview of Supply Chain Choreographer for Tanzu in the VMware Tanzu Application Platform Documentation.
    4. Specify the parameters for the Image registry provider, including the secret name, the project path, and the secret namespace. These credentials are for pushing and pulling application images.
      You can optionally click Create Secret to configure a new registry secret or opaque secret.
    5. Select the Namespace provisioner, either Controller or GitOps, and then configure the parameters for the selected provisioner.
      For more information about Namespace provisioner, see Overview of Namespace Provisioner in the VMware Tanzu Application Platform Documentation.
    6. You can optionally expand the Configure the Git repository section and change the default settings.
    7. The Cluster URL is populated when you select the cluster. You can change it if needed.
    8. The CA certificate is populated when you select the cluster. You can change it if needed.
    9. Optionally, you can expand the Advanced Configuration section of the page to configure parameters in the configuration form or YAML.
      Note: To install the Iterate profile with all build dependencies, add the following section to the YAML configuration. 
      buildservice:
  exclude_dependencies: true
  11. Click Add Profile to install a TAP profile on another cluster.
  12. Click Done when finished configuring profiles on clusters.
  13. Click View License Agreement to read the agreement, then click Close and Accept to agree to the license terms.
    You must accept the VMware license agreement to continue with the installation. The option for inclusion in the Customer Experience Improvement Program must also be enabled for the TAP installation to proceed.
  14. Click Install TAP.

Results

When you click Install TAP, Tanzu Mission Control installs Tanzu Application Platform and the configured profiles on the clusters that you specified.
Note: When installing or upgrading a Tanzu Application Platform (TAP) deployment on your cluster, you might encounter an intermediate state of installation failure with one or more packages. This situation can be safely ignored, as it is only temporary. After a short period of time, these issues are reconciled to a state of installation success.

What to do next

To view information about the installations, go to the Solutions tab on the Catalog page, and then click Installed Tanzu Application Platforms. From this page, you can do the following:
  • Verify the profile details and status of all packages installed.
  • Edit the configuration of a TAP installation.
  • Delete a TAP installation.

To learn more about Tanzu Application Platform, see the latest version of the VMware Tanzu Application Platform Documentation.