Open yann-soubeyrand opened 1 month ago
This issue has not had any activity in the past 30 days, so the needs-attention
label has been added to it.
If the opened issue is a bug, check to see if a newer release fixed your issue. If it is no longer relevant, please feel free to close this issue.
The needs-attention
label signals to maintainers that something has fallen through the cracks. No action is needed by you; your issue will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!
What's wrong?
Hi,
I’ve used the facility offered by https://github.com/grafana/alloy/pull/820 to change the name of the port on the cluster service to
tcp
so that clustering works when deploying Alloy on Istio. However, I can’t get it to work. I’ve had to also change the name of the “normal” service totcp
to get clustering to work.Steps to reproduce
Deploy Alloy using the Helm chart and the following values:
Look at the state of Alloy clustering (from the web UI) and see that the cluster is only composed of the local node.
One can see the following in Istio access logs:
System information
Kubernetes on Linux AMD64 nodes
Software version
Grafana Alloy v1.3.0 deployed using Helm chart v0.6.0
Configuration
No response
Logs
No response