Component(s)
No response
Request
Please add Gateway API HTTPRoute support in the alloy Helm chart. Right now, the only way to expose alloy externally is ingress. This means we can only use Ingress controllers.
There is already a precedent in Grafana. The pyroscope chart has an httpRoute key (you can see the template here: operations/pyroscope/helm/pyroscope/templates/httpRoute.yaml).
Desired behavior:
- It should be disabled by default.
- When enabled, the default behavior should be the same as the current
ingress configuration (one rule for the Faro port).
Use case
Our clusters run on Istio, and we do not use NGINX Ingress anymore. Because of this, we currently have to keep our route configuration outside the chart.
I know we can use extraObjects as a workaround. However, this is not convenient for us because it makes the configuration messy and harder to maintain. We prefer to keep all related settings inside the standard chart values.
Note: This is related to issue #5157, but it is a different request. That issue asks for a built-in NGINX gateway, but we only need standard HTTPRoute support.
AI disclosure
Tip
React with 👍 if this issue is important to you.
Component(s)
No response
Request
Please add Gateway API HTTPRoute support in the
alloyHelm chart. Right now, the only way to exposealloyexternally isingress. This means we can only use Ingress controllers.There is already a precedent in Grafana. The
pyroscopechart has anhttpRoutekey (you can see the template here: operations/pyroscope/helm/pyroscope/templates/httpRoute.yaml).Desired behavior:
ingressconfiguration (one rule for the Faro port).Use case
Our clusters run on Istio, and we do not use NGINX Ingress anymore. Because of this, we currently have to keep our route configuration outside the chart.
I know we can use
extraObjectsas a workaround. However, this is not convenient for us because it makes the configuration messy and harder to maintain. We prefer to keep all related settings inside the standard chart values.Note: This is related to issue #5157, but it is a different request. That issue asks for a built-in NGINX gateway, but we only need standard HTTPRoute support.
AI disclosure
Tip
React with 👍 if this issue is important to you.