{{.Release.Name}}-container-agent configmap override.

[from-nibly]

We have a lot of similar resourceClasses that just have different resource limits/requests. Each one needs a fairly big list of configuration to get working in our cluster though.

Templating in the values.yml file isn't really an option; however, creating the configmap is trivial.

The only problem is that the template for the configmap in the original chart always renders the configmap, so if I add my own configmap named the same thing it shows as a warning in ArgoCD. While this works, it's not ideal.

It would be great if the configmap only rendered if there were resourceClasses or if there was an option to explicitly not render the configmap.

Will submit a PR to add greater detail

[from-nibly]

PR #81

[jrahme-cci]

Hey, @from-nibly thanks for the PR. You bring up a really good use case. I'll take a look at it this week.

[jrahme-cci]

After discussing with the team, we agree with your use case but are going to take a different approach; to allow a configmap to be specified in the values.yaml as a source for resource classes in addition to the classes generated from any definitions included in the values.yaml file.

I'll leave this issue open and link it to our internal ticket, and will update here once we have the feature shipped. Thanks for your input :)