A
Alabaster Grouse
We have over 60 Kubernetes clusters that all have their own delegates, and some of those clusters are created/destroyed regularly.
We strive to have cluster provisioning 100% automated, and It would be very helpful if CCM connectors could be automatically added when setting a value
true
in the helm
values.yaml
files for the delegates.
We find that users forget to go into CCM and set up the connector to collect data because it's a manual step. We discover that someone forgot to do this work weeks/months later when we want to look for cost data, only to find it isn't there.
(Side note: We would also like to avoid having to add additional automation that calls harness APIs after a cluster is built.)