Next steps

[prydonius]

After talking with @technosophos on Slack, it became clear to us that what we're trying to do here leads to some awkward configurations for more complex charts (e.g. see the deployment in https://gist.github.com/prydonius/30747d0bbee3487b1b67b4454d65b423 - there's a mix of stuff in values.yaml and awkward syntax is the deployment itself). It works nice for the simple cases like services, but quickly becomes more difficult if you need to do stuff with values in the resources.

We're thinking it might be better to take a lighter approach, rather than try to abstract away the full Kubernetes objects, we can just create a bunch of helper functions for reducing boilerplate for common snippets like labels, volumes, resources, etc.

[prydonius]

cc @pierreozoux who was working on a common Ingress template in helm/charts#794

[pierreozoux]

About the description of the resources, everything is in the PR and the issue linked above.

About the helpers, I have the feeling that if we need helpers, helm users need them too, so they should be merged there.