This topic tells you how to validate the implementation of a multicluster topology by taking a sample workload and passing it by using the supply chains on the Build and Run clusters.
Use this topic to build an application on the Build profile clusters and run the application on the Run profile clusters.
You can view the workload and associated objects from Tanzu Application Platform GUI (commonly known as TAP GUI) interface on the View profile cluster.
You can take various approaches to configuring the supply chain in this topology, but the following procedures validate the most basic capabilities.
Before implementing a multicluster topology, complete the following:
Complete all installation steps for the four profiles: Build, Run, View and Iterate.
For the sample workload, VMware uses the same Application Accelerator - Tanzu Java Web App in the non-multicluster Get Started guide. You can download this accelerator to your own Git infrastructure of choice. You might need to configure additional permissions. Alternatively, you can also use the application-accelerator-samples GitHub repository.
The two supply chains are ootb-supply-chain-basic on the Build/Iterate profile and ootb-delivery-basic on the Run profile. For the Build/Iterate and Run profiled clusters, perform the steps described in Setup Developer Namespace. This guide assumes that you use the default namespace.
To set the value of DEVELOPER_NAMESPACE to the namespace you setup in the previous step, run:
export DEVELOPER_NAMESPACE=YOUR-DEVELOPER-NAMESPACE
Where:
YOUR-DEVELOPER-NAMESPACE is the namespace you set up in Set up developer namespaces to use your installed packages. default is used in this example.The Build cluster starts by building the necessary bundle for the workload that is delivered to the Run cluster.
Use the Tanzu CLI to start the workload down the first supply chain:
tanzu apps workload create tanzu-java-web-app \
--git-repo https://github.com/vmware-tanzu/application-accelerator-samples \
--sub-path tanzu-java-web-app \
--git-branch main \
--type web \
--label app.kubernetes.io/part-of=tanzu-java-web-app \
--yes \
--namespace ${DEVELOPER_NAMESPACE}
To monitor the progress of this process, run:
tanzu apps workload tail tanzu-java-web-app --since 10m --timestamp --namespace ${DEVELOPER_NAMESPACE}
To exit the monitoring session, press CTRL + C.
Generate the deliverable.yaml file.
deliverable.yaml file for Tanzu Application Platform v1.3.5 and later:
Verify that your supply chain has produced the necessary ConfigMap containing Deliverable content produced by the Workload:
kubectl get configmap tanzu-java-web-app-deliverable --namespace ${DEVELOPER_NAMESPACE} -o go-template='{{.data.deliverable}}'
The output resembles the following:
apiVersion: carto.run/v1alpha1
kind: Deliverable
metadata:
name: tanzu-java-web-app
labels:
apis.apps.tanzu.vmware.com/register-api: "true"
app.kubernetes.io/part-of: tanzu-java-web-app
apps.tanzu.vmware.com/workload-type: web
app.kubernetes.io/component: deliverable
app.tanzu.vmware.com/deliverable-type: web
spec:
params:
- name: gitops_ssh_secret
value: ""
source:
git:
url: http://git-server.default.svc.cluster.local/app-namespace/tanzu-java-web-app
ref:
branch: main
Store the Deliverable content, which you can take to the Run profile clusters from the ConfigMap by running:
kubectl get configmap tanzu-java-web-app-deliverable -n ${DEVELOPER_NAMESPACE} -o go-template='{{.data.deliverable}}' > deliverable.yaml
deliverable.yaml file for Tanzu Application Platform v1.3.2 and 1.3.4:
Verify that your supply chain has produced the necessary ConfigMap containing Deliverable content produced by the Workload:
kubectl get configmap tanzu-java-web-app --namespace ${DEVELOPER_NAMESPACE} -o go-template='{{.data.deliverable}}'
The output resembles the following:
apiVersion: carto.run/v1alpha1
kind: Deliverable
metadata:
name: tanzu-java-web-app
labels:
app.kubernetes.io/component: deliverable
app.tanzu.vmware.com/deliverable-type: web
spec:
params:
- name: gitops_ssh_secret
value: ""
source:
git:
url: http://git-server.default.svc.cluster.local/app-namespace/tanzu-java-web-app
ref:
branch: main
Store the Deliverable content, which you can take to the Run profile clusters from the ConfigMap by running:
kubectl get configmap tanzu-java-web-app -n ${DEVELOPER_NAMESPACE} -o go-template='{{.data.deliverable}}' > deliverable.yaml
deliverable.yaml file for Tanzu Application Platform v1.3.0:
Verify that your supply chain has produced the necessary Deliverable for the Workload by running:
kubectl get deliverable --namespace ${DEVELOPER_NAMESPACE}
The output should look simiar to the following:
kubectl get deliverable --namespace default
NAME SOURCE DELIVERY READY REASON AGE
tanzu-java-web-app tapmulticluster.azurecr.io/tap-multi-build-dev/tanzu-java-web-app-default-bundle:xxxx-xxxx-xxxx-xxxx-xxxxx False DeliveryNotFound 28h
The Deliverable contains the reference to the source. In this case, it is a bundle on the image registry you specified for the supply chain. The supply chains can also leverage Git repositories instead of ImageRepositories, but that’s beyond the scope of this tutorial.
Create a Deliverable after verifying there’s a Deliver on the build cluster. Copy its content to a file that you can take to the Run profile clusters:
kubectl get deliverable tanzu-java-web-app --namespace ${DEVELOPER_NAMESPACE} -oyaml > deliverable.yaml
Delete the ownerReferences and status sections from the deliverable.yaml.
After editing, the file will look like the following:
apiVersion: carto.run/v1alpha1
kind: Deliverable
metadata:
creationTimestamp: "2022-03-10T14:35:52Z"
generation: 1
labels:
app.kubernetes.io/component: deliverable
app.kubernetes.io/part-of: tanzu-java-web-app
app.tanzu.vmware.com/deliverable-type: web
apps.tanzu.vmware.com/workload-type: web
carto.run/cluster-template-name: deliverable-template
carto.run/resource-name: deliverable
carto.run/supply-chain-name: source-to-url
carto.run/template-kind: ClusterTemplate
carto.run/workload-name: tanzu-java-web-app
carto.run/workload-namespace: default
name: tanzu-java-web-app
namespace: default
resourceVersion: "635368"
uid: xxxx-xxxx-xxxx-xxxx-xxxx
spec:
source:
image: tapmulticluster.azurecr.io/tap-multi-build-dev/tanzu-java-web-app-default-bundle:xxxx-xxxx-xxxx-xxxx-xxxx
Take this Deliverable file to the Run profile clusters by running:
kubectl apply -f deliverable.yaml --namespace ${DEVELOPER_NAMESPACE}
(v1.3.2 to v1.3.4 only) Patch the Deliverable created on the Run profile cluster to add missing labels. See known issues.
kubectl patch deliverable tanzu-java-web-app \
-n ${DEVELOPER_NAMESPACE} \
--type merge \
--patch "{\"metadata\":{\"labels\":{\"carto.run/workload-name\":\"tanzu-java-web-app\",\"carto.run/workload-namespace\":\"${DEVELOPER_NAMESPACE}\"}}}"
Verify that this Deliverable is started and Ready by running:
kubectl get deliverables --namespace ${DEVELOPER_NAMESPACE}
The output resembles the following:
kubectl get deliverables --namespace default
NAME SOURCE DELIVERY READY REASON AGE
tanzu-java-web-app tapmulticloud.azurecr.io/tap-multi-build-dev/tanzu-java-web-app-default-bundle:xxxx-xxxx-xxxx-xxxx-1a7beafd6389 delivery-basic True Ready 7m2s
To test the application, query the URL for the application. Look for the httpProxy by running:
kubectl get httpproxy --namespace ${DEVELOPER_NAMESPACE}
The output resembles the following:
kubectl get httpproxy --namespace default
NAME FQDN TLS SECRET STATUS STATUS DESCRIPTION
tanzu-java-web-app-contour-a98df54e3629c5ae9c82a395501ee1fdtanz tanzu-java-web-app.default.svc.cluster.local valid Valid HTTPProxy
tanzu-java-web-app-contour-e1d997a9ff9e7dfb6c22087e0ce6fd7ftanz tanzu-java-web-app.default.apps.run.multi.kapplegate.com valid Valid HTTPProxy
tanzu-java-web-app-contour-tanzu-java-web-app.default tanzu-java-web-app.default valid Valid HTTPProxy
tanzu-java-web-app-contour-tanzu-java-web-app.default.svc tanzu-java-web-app.default.svc valid Valid HTTPProxy
Select the URL that corresponds to the domain you specified in your Run cluster’s profile and enter it into a browser. Expect to see the message “Greetings from Spring Boot + Tanzu!”.
View the component in Tanzu Application Platform GUI, by following these steps and using the catalog file from the sample accelerator in GitHub.
