Alloy Clustering mode is currently incompatible with running inside an Istio mesh when deployed via the Helm Chart

[josh-thisisbud]

What's wrong?

Currently this Alloy chart is falling into this trap when run with Istio as a sidecar - https://istio.io/latest/docs/ops/common-problems/network-issues/#503-error-while-accessing-headless-services

The fix is relatively simple, either;

• Allow the end user to specify the port name used instead of hardcoding it to http. This will allow istio users to fallback to the TCP support which would work for this traffic.
• Alternatively, send a host header containing the hostname which was looked up on the request to join a cluster

Steps to reproduce

Install Alloy via the helm chart on a Kubernetes cluster running Istio in strict mode and with allow_any traffic profile enabled. Have Alloy run with an istio sidecar. Attempt to turn on clustering mode. See that no nodes are able to communicate with each other.

System information

No response

Software version

Alloy v1.0.0

Configuration

No response

Logs

No response

[josh-thisisbud]

@rfratto As we use the published helm chart, how would I go about getting a new version cut with this fix in it? Is it done on a specific schedule? Could it already be done and I'm just not seeing it on ArtifactHub?

[rfratto]

@josh-thisisbud We don't have a normal release cadence for the Helm chart. We typically put out a release when enough changes accumulate. But since you're waiting for this change and I don't know of any alternatives to use a non-release version, I'll open a PR to release a new version now.

[josh-thisisbud]

Thank you!

…

On Wed, 22 May 2024, 14:06 Robert Fratto, ***@***.***> wrote: @josh-thisisbud <https://github.com/josh-thisisbud> We don't have a normal release cadence for the Helm chart. We typically put out a release when enough changes accumulate. But since you're waiting for this change and I don't know of any alternatives to use a non-release version, I'll open a PR to release a new version now. — Reply to this email directly, view it on GitHub <#800 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AY5KNPB6PTZCXC2MFMHT73LZDSJ4BAVCNFSM6AAAAABHNEUSSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRUG42TEOJWGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>