You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @Hronom! This is definitely something on our radar. We have recently published our API docs for Collections which may help you integrate Collections into your GitOps workflow while we develop a helm values driven approach to Collection
@kwombach12 It would be great, if the collections could also be provided outside of Helm values by pointing the chart to an existing configmap (or even better to collect configmaps with a certain label and mounting those, e.g. like the Grafana and Prometheus Chart do this using sidecars). This would allow a platform team to just add configmaps to the namespace without having to hardcode these things in a single values file.
Problem Statement
Right now there no possibility to manage collections using helm values.
This not allow to leverage fully GitOps approach with combination of Argo CD.
Solution Description
Provide possibility to manage collections in Kubecost through helm values.
Alternatives
No response
Additional Context
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: