Describe the bug a clear and concise description of what the bug is.
Using 80.10.0
(might be related to #6434)
What's your helm version?
v3.19.0
What's your kubectl version?
Client Version: v1.35.1 Kustomize Version: v5.7.1 Server Version: v1.35.1
Which chart?
kube-promtheus-stack
What's the chart version?
80.10.0
What happened?
There are various alerts, such as etcdMembersDown, which are false positives. I so far verified for etcd that the listening address for metrics is [::1]:2381, while the scraping address is the ipv6 address of the eth0 interface. This does obviously not work. There are further alerts which I assume are related
What you expected to happen?
To have kube-prometheus-stack pickup the localhost listener instead of the host ip address listener.
How to reproduce it?
Deploy a single node k8s cluster, one control plane.
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
no command, monitoring fails
Anything else we need to know?
No response
Describe the bug a clear and concise description of what the bug is.
Using 80.10.0
(might be related to #6434)
What's your helm version?
v3.19.0
What's your kubectl version?
Client Version: v1.35.1 Kustomize Version: v5.7.1 Server Version: v1.35.1
Which chart?
kube-promtheus-stack
What's the chart version?
80.10.0
What happened?
There are various alerts, such as etcdMembersDown, which are false positives. I so far verified for etcd that the listening address for metrics is [::1]:2381, while the scraping address is the ipv6 address of the eth0 interface. This does obviously not work. There are further alerts which I assume are related
What you expected to happen?
To have kube-prometheus-stack pickup the localhost listener instead of the host ip address listener.
How to reproduce it?
Deploy a single node k8s cluster, one control plane.
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
no command, monitoring fails
Anything else we need to know?
No response