Without this, certainly malformed CR could trigger Prometheus config parsing error, distrupting the whole cluster collection config changes.
Also to provide better fix to potentially #479 (vs creating separate CR) we could add e.g. JobNameSuffix field for endpoint, but that's for another PR.
Related to https://github.com/GoogleCloudPlatform/prometheus-engine/issues/479
Without this, certainly malformed CR could trigger Prometheus config parsing error, distrupting the whole cluster collection config changes.
Also to provide better fix to potentially #479 (vs creating separate CR) we could add e.g. JobNameSuffix field for endpoint, but that's for another PR.