Before installing multicluster Tanzu Application Platform profiles, you must meet the following prerequisites:
The installation order is flexible given the ability to update the installation with a modified values file using the
tanzu package installed update command. The preceding is an example of the order of operations to be used:
Update the View cluster’s installation values file with the previous information and run the following command to pass the updated config values to Tanzu Application Platform GUI:
tanzu package installed update tap -p tap.tanzu.vmware.com -v TAP-VERSION --values-file tap-values.yaml -n tap-install
TAP-VERSION is the Tanzu Application Platform version you’ve installed
Install the View profile cluster first, because some components must exist before installing the Run clusters. For example, the Application Live View back end must be present before installing the Run clusters. For more information about profiles, see About Tanzu Application Platform package profiles.
To install the View cluster:
INGRESS-DOMAINis the DNS domain you set in
shared.ingress_domainwhich points to the shared Contour installation in the
tanzu-system-ingressnamespace with the service
To install the Build profile cluster:
To install the Run profile cluster:
To use Application Live View, set the
appliveview_connector to match the value you set on the View profile for the
appliveview in the values file.
Note: The default configuration of
shared.ingress_domainpoints to the local Run cluster, rather than the View cluster, as a result,
shared.ingress_domainmust be set explicitly.
Service Accountsthat Tanzu Application Platform GUI uses to read objects from the clusters.
After setting up the 3 profiles, you’re ready to run a workload by using the supply chain. See Getting started with multicluster Tanzu Application Platform.