Give an way in helm deploy to change the root asset path
Open
Nobody has claimed this yet.
New feature
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Helm chart's configurable values and how deployment settings reach the QuestDB console's asset_path. Verify the behavior with an ingress path other than "/" on AKS. Done means a Helm deployment can set the asset path and the console loads its JavaScript and CSS correctly through that ingress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, helm, kubernetes
- Domain
- devops, frontend, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100