"Impact: Teams would not be able to deploy their applications without some solution to this problem, even if it is keeping a static set of Helm charts, one per environment. The toil from the maintenance on this approach as well as the potential for cut and paste errors would be high.

Workaround: We can continue maintaining the processes and approaches we have outside of Harness to support these use cases, passing in the appropriate Helm charts into the pipelines as needed.

Request: We need the ability to parse a hierarchy of values which leverages inheritance to define a set of values that applies to a specific target cluster. These values are injected into Helm templates at or before deploy time to create a valid Helm chart for that specific cluster based on team-defined values. For example, you might have 4 pods in EMEA and only 2 pods in the US. You write your values files in such a way that the system knows that all the Helm charts destined for EMEA clusters use the value 4 and the US clusters use 2.