-
Notifications
You must be signed in to change notification settings - Fork 6.9k
Description
What happened?
etcd metrics are not be available in the Prometheus instance of the kube prometheus stack if the service labels are misconfigured.
What did you expect to happen?
I expected, based on the provided documentation, that metrics would be available in the Prometheus instance deployed with the "kube-prometheus-stack".
How can we reproduce it (as minimally and precisely as possible)?
Current documentation: (https://kubespray.io/#/docs/operations/etcd?id=metrics)
etcd_deployment_type: host
etcd_metrics_port: 2381
etcd_metrics_service_labels:
k8s-app: etcd
app.kubernetes.io/managed-by: Kubespray
app: kube-prometheus-stack-kube-etcd
release: prometheus-stack
In Helm chart of kube prometheus stack:
kubeEtcd:
service:
enabled: false
Corrected value for release:
etcd_metrics_service_labels:
k8s-app: etcd
app.kubernetes.io/managed-by: Kubespray
app: kube-prometheus-stack-kube-etcd
release: kube-prometheus-stack
After updating the release label as shown above, metrics become available in the kube prometheus stack. Therefore, it would make sense to update the documentation to reflect this change.
OS
Ubuntu 24
Version of Ansible
ansible-core==2.17.3
Version of Python
Python 3.12.3
Version of Kubespray (commit)
2.29.1
Network plugin used
cilium
Full inventory with variables
etcd_deployment_type: host
etcd_metrics_port: 2381
etcd_metrics_service_labels:
k8s-app: etcd
app.kubernetes.io/managed-by: Kubespray
app: kube-prometheus-stack-kube-etcd
release: kube-prometheus-stack
Command used to invoke ansible
Ansible Semaphore
Output of ansible run
N/A
Anything else we need to know
No response