[Enhancement]: Monitoring of custom resources #10276
Labels
Comments
sebastiangaiser
added a commit
to sebastiangaiser/strimzi-kafka-operator
that referenced
this issue
Jun 28, 2024
…state In order to monitor the state of custom resources (CR) inside of the Kubernetes cluster, kube-state-metrics can be deployed. This describes the deployment using the prometheus-community Helm chart. Issue: strimzi#10276 Signed-off-by: Sebastian Gaiser <sebastiangaiser@users.noreply.github.com>
8 tasks
8 tasks
|
Discussed on the community call on 10.7.2024: Looks good to Jakub & Jakub 😉. But should be discussed on the next call with hopefully more maintainers present. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related problem
In #9802 there was a discussion about how to monitor the state of a custom resources (CR) like
KafkaTopic,KafkaUser, ... .Suggested solution
There was a suggestion to use kube-state-metrics (ksm) to monitor the state of each CR. For deploying the
kube-state-metrics, personally I would recommend using the kube-state-metrics Helm chart which is already part of the kube-prometheus-stack (via a sub-chart).Using ksm relies on the status object of a Kubernetes resource.
Alternatives
No response
Additional context
Flux also handle this via
kube-state-metrics.:Flux documentation: https://fluxcd.io/flux/monitoring/custom-metrics/
Flux example repository: https://github.com/fluxcd/flux2-monitoring-example
The text was updated successfully, but these errors were encountered: