Target Cluster shown “Workload not applied to target” with the supplychain plugin in TAP GUI after upgrading TAP v1.3.2-1.3.4 and v1.4.0

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

The multi-cluser instruction is not working with the supplychain plugin in TAP GUI after upgrading TAP v1.3.2-1.3.4 and v1.4.0. “Target Cluster” shown “Workload not applied to target”.



 

The Cause:

This issue is related to the known issue of Supply Chain Choreographer. Please kindly check TAP known issue note to get more information: https://techdocs.broadcom.com/us/en/vmware-tanzu/spring/api-portal-for-tanzu/1-5/api-portal-tanzu/index.html

 

Supply Chain Choreographer
On a Build profile cluster, a ConfigMap containing the Deliverable is now produced. Previously a Deliverable was created directly on the cluster.

In a Build profile cluster, deliverables are created with the labels to associate them with their Workload missing. As a workaround, they will have to be manually injected.
These Deliverables are now rendered inside a ConfigMap. This resource was not renamed, and will cause Cartographer to overwrite one deliverable with the other depending on the timing of events in your cluster.

Environment

Product Version: 1.3

Resolution

Workaround:

For TAP v1.3.2 to v1.3.4 and v1.4.0, Patch the Deliverable created on the Run profile cluster to add missing labels.

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}\"}}}"

To get more information, please kindly refer to
https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-application-platform/1-11/tap/multicluster-getting-started.html

https://techdocs.broadcom.com/us/en/vmware-tanzu/spring/api-portal-for-tanzu/1-4/api-portal-tanzu/operator-guide.html

 

 

Fix:

This known issue is fixed in TAP v1.3.5+ and v1.4.1+.