search

grafana / alloy

OpenTelemetry Collector distribution with programmable pipelines
https://grafana.com/oss/alloy
Apache License 2.0
1.38k stars 201 forks source link

Enable Ingress on the Grafana Agent Flow UI in Kubernetes environments #404

Open jsd7599 opened 1 year ago

jsd7599 commented 1 year ago

Request

Is there an option to enable ingress on the Grafana Agent Flow UI? The helm chart values.yaml file seems to only suggest enabling ingress for faro -> https://github.com/grafana/agent/blob/main/operations/helm/charts/grafana-agent/values.yaml

Use case

To have a similar options to whats available here for Kubernetes kind:ingress & make it editable via the Grafana Agent Flow UI -> https://github.com/grafana/agent/blob/main/operations/helm/charts/grafana-agent/templates/ingress.yaml

thampiotr commented 1 year ago

cc @tpaschalis I assume that we'd also need to have a service for this. One caveat is that such ingress would redirect you to a random instance of the agent, so while it can be useful for debugging some issues, it may be not so useful when a user wants to reach a specific instance.

rfratto commented 1 year ago

Don't Ingresses usually imply publicly exposing a resource to the internet? I'm not sure if that's something we want to encourage with the Flow UI, since the UI might expose some sensitive information, even if it hides all API keys.

Can you expand on your use case and what you're trying to accomplish here?

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had any activity in the past 30 days. The issue will not be closed automatically, but a label will be added to it for tracking purposes.

If the opened issue is a bug, check if newer releases have fixed the issue. If the issue is no longer relevant, please feel free to close it. Thank you for your contributions!