We considered keeping all the charts together in one repo. But it's just simpler for developers. I can't say I'm thrilled to put deployment-specific values in

We considered keeping all the charts together in one repo. But it's just simpler for developers. I can't say I'm thrilled to put deployment-specific values in the repo. Maybe the solution is to keep the chart itself, with its defaults, in the repo, and then have a configmap or third-party resource in Kubernetes that contains the values. To deploy anything, you use the Kubernetes API to find the app's values and merge them into the template. I wouldn't be surprised if one day Kubernetes might support that kind of templating. I also wonder what kind of system Google uses internally. They have been rather silent about offering good advice here.