[helm] Check for ServiceMonitor apiVersion capabilities #1457
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
In an Kubernetes as a Service Environment the values.yaml for the sealed-secrets are predefined.
This means also that the Monitoring is enabled by default.
Enabling the ServiceMonitor and not have the kube-prometheus-stack in place leads to issues installing this chart.
The kube-prometheus-stack releates on some pre defined secrets thats why the sealed-secrets deployment is needed before the kube-prometheus-stack.
Also enabling and disabling this leads to some commits in an gitops approach way.
Thats why i would like to have this capabilities check in place.
Benefits
The ServiceMonitor is not applyed unless the approappropriate crd is installed.
Possible drawbacks
helm template will not render the ServiceMonitor object if it does not know about this api capabilities or the --validate flag is not provided.