-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gaia baseURL configuration for proxy support #124
Comments
Doesn't your ingress proxy provide you with the capability to rewrite traffic to a certain port when coming from a certain path? Gaia could be running on 9999 and anything that comes to /pipeline/ can be rewritten and routed to /:9999. Why would you need to serve gaia under /pipeline/ for this? Infact gaia could be just another service running in a different pod that your ingress routed to. |
Difficulty comes with html content which directs itself back or serves itself from /, e.g. assets. Most proxys wont intercept this traffic and rewrite the html before delivery. Other monitoring tools e.g. grafana provide this capability |
Jaeger also had an issue regards this which we could consider jaegertracing/jaeger-ui#42 |
I see. Carry on then. |
I am currently looking at implementing Gaia in my K8 cluster alongside other DevOps tooling. To integrate it with my ingress proxy I would like to be able to serve gaia under a sub directory e.g. /pipeline/...
Current configuration does not allow me to specific the baseURL
The text was updated successfully, but these errors were encountered: