When using k8s-sidecar to manage the router/distributor Thanos component's hashrings configuration, a label is required to discover the correct ConfigMap, this change adds the ability to define a custom label, through the use of --configmap-generated-custom-label that will be adding to the "generated" ConfigMap.
What does this change solve?
When using k8s-sidecar to manage the router/distributor Thanos component's hashrings configuration, a label is required to discover the correct ConfigMap, this change adds the ability to define a custom label, through the use of
--configmap-generated-custom-labelthat will be adding to the "generated" ConfigMap.