This topic lists known issues for Tanzu Supply Chains.
CautionTanzu Supply Chain is currently in beta and is not intended for production use. It is intended only for evaluation purposes for the next generation Supply Chain. For the current Supply Chain solution, see the Supply Chain Choreographer documentation.
Workloads
in the same namespace where the SupplyChain
is installed. This will be fixed in the future versions before Tanzu Supply Chains becomes GA and SupplyChain
will be installed inprotected namespace(s) in the cluster based on Platform Engineer preferences. Developers will be able to create Workloads
in any namespace as long as they have permissions to do so in that namespace.WorkloadRuns
and thereby not visible in the tanzu workload run get
outputs.Component
pipelines and exposed as a message is not properly propagated in the status of the WorkloadRun
and thereby not visible in the tanzu workload run get
outputs.WorkloadRuns
are not being correctly created upon changes triggered by these resumptions. The current workaround is to assess all triggers in a single resumption.Pipelines
and Tasks
are currently running in the Developer namespace where the Workload
is. In future release, SupplyChain
namespaces will run these resources for the Component
unless its specifically chosen by the component author to run in the Developer namespace. There are use cases for components such as source-git-provider
where a Developer can provide a secret to pull the source for their repository without the Platform Engineer being the bottleneck.