Overriding helm values for applications installed with Jenkins X is getting confusing. There are lots of places where helm values exists, taking tekton for example you can configure values in the main chart
https://github.com/jenkins-x-charts/tekton/blob/master/tekton/values.yaml
or look for the right version stream configured for your cluster and check the chart template values
https://github.com/jenkins-x/jxr-versions/blob/master/charts/jenkins-x/tekton/template-values.yaml
or the app template values
https://github.com/jenkins-x/jxr-versions/blob/master/apps/jenkins-x/tekton/values.yaml.gotmpl
and also possibly the boot config repo where we would recommend folks override values
i.e. apps/tekton/values.yaml
or to be able to use jxRequirements.yaml as parameters we can also use a gotmpl file
apps/tekton/values.yaml.gotmpl
Note this is different to a Helmfile gotmpl file as only jxRequirements are supported template options.
https://github.com/roboll/helmfile#templating which again could cause confusion.
Its kinda hard to grok whats needed and which way we should go. Right now we are working on a different boot config repos, one for Vault another for GSM, we are changing each of them a bit to tailor them for their specific needs, we need to somehow sync or share changes between boot config repos.
Folks will likely be overwhelmed by all the options and find it hard to navigate around the repos. It would be good to see if we can find a way to cut down on all the values override options so that it's easier for users to grok and simpler examples to follow, hopefully having a single place where people can look?