Open jsd7599 opened 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.
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?
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!
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