[prometheus][deckhouse] Add supporting ServiceMonitors and PodMonitors from user-space #604
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
Change
podMonitorNamespaceSelector
andserviceMonitorNamespaceSelector
from labelheritage: deckhouse
to new customprometheus.deckhouse.io/monitor-watcher-enabled
label. Because we do not want give an opportunity for usageheritage: deckhouse
label for non-deckhouse namespaces, but we need pass namespace selectors into Prometheus resource. We can not implement OR logic with LabelSelector and we should change labels.Add
prometheus.deckhouse.io/monitor-watcher-enabled
tod8-monitoring
namespace. All own Pod and Service Monitor located ind8-monitoring
namespace.Add FAQ for connect user-space Service/Pod Monitors to Prometheus.
Change alert description about custom monitors.
Custom monitors alert logic did not change, because it already has correct logic.
Why do we need it, and what problem does it solve?
There is no way to connect custom ServiceMonitor to Prometheus from Deckhouse. However, all modern helm charts are bundled with a ServiceMonitor. Users have to alter charts to provide monitoring.
Changelog entries