Add ability to define optional nodeSelector, which will be used in mimir-proxy-deployment-template.yaml template.
Not sure, but probably it could be set in spec.values.global.mimirProxy or create a new section for it.
Btw, it's also impossible to define resources requests/limits for mimir-proxy, which would be useful to add as well I think. Since now they're not set.
Alternatives
No response
Additional Context
I can prepare PR for this feature if solution sounds good.
Troubleshooting
[X] I have read and followed the issue guidelines and this is a feature request only for the Helm chart.
[X] I have searched other issues in this repository and mine is not recorded.
Problem Statement
mimir-proxy was added in https://github.com/kubecost/cost-analyzer-helm-chart/pull/2201 and from my understanding, now it's impossible to set nodeSelector via Helm values, since it's missing in template https://github.com/kubecost/cost-analyzer-helm-chart/blob/develop/cost-analyzer/templates/mimir-proxy-deployment-template.yaml
Solution Description
Add ability to define optional nodeSelector, which will be used in
mimir-proxy-deployment-template.yamltemplate. Not sure, but probably it could be set inspec.values.global.mimirProxyor create a new section for it.Btw, it's also impossible to define resources requests/limits for mimir-proxy, which would be useful to add as well I think. Since now they're not set.
Alternatives
No response
Additional Context
I can prepare PR for this feature if solution sounds good.
Troubleshooting