Give an way in helm deploy to change the root asset path

[mfandre]

Is your feature request related to a problem?

I installed questDB to my AKS cluster using helm, but my ingress is looking to route that is different from "/". The questdb console is trying to get js/css files from wrong root path.

Describe the solution you'd like.

Add some env var that can be set on helm deploy to change the asset_path value.

Describe alternatives you've considered.

No response

Additional context.

No response

[pswu11]

Issue is also created in the questdb kubernetes repo: https://github.com/questdb/questdb-kubernetes/issues/53

[jerrinot]

I learned from @insmac that's the asset path as documented here is actually a build-time option, not a runtime option. So making this configurable for end-users will need changes in both QuestDB-Core and QuestDB-Kubernetes repos.

[mfandre]

To avoid this behavior I created a subdomain to maintain the root path. But I think this an important feature that can be useful to others.

[mounte]

Just wanted to send my +1 for this. I have a setup where envoy or traefik is put in front of questdb and some other services where subdomains are limited so we use envoy to route based on the path prefix. It works great for the exec and exp endpoints but if we try to pass the web-ui through the proxy it can not find the resources needed.

We would wish for some env-variable or setting that questdb picks up on and allows the web-ui to be served from some path other than /

[jerrinot]

This was fixed in the latest web console and the next QuestDB version will include this change.

This means it'll be possible to have an ingress_controller / reverse_proxy where QuestDB is mapped under a non-root context.

I tested it with a local nginx:

location /quest/ {
            proxy_pass http://localhost:9000/;
        }

and it's working like a charm!