charts/wire-server-metrics: Use kube-prometheus-stack #1915
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.
The old version of prometheus operator chart is no longer compatible with latest
K8s versions. The chart has also since moved to kube-prometheus-stack on the
prometheus-community helm chart reposistory from the helm-stable repository.
The kube-prometheus-stack helm chart also allows creating dashboard using labels
on configmaps, so now we don't have to refer to non-pinned versions of the
dashboard definitions. Instead each dashboard now becomes a configmap with a
specific label and grafana discovers it.
This commit also updates the dashboards to use new ways of addressing the pods
which came with the move from old version of prometheus-operator chart to the
kube-prometheus-stack chart. Along with these changes, the dashboards now also
use the qualified endpoints and federation endpoints to display information
about prekey claims and message sending stats.
https://wearezeta.atlassian.net/browse/FS-64
Checklist
changelog.d
.