Skip to content
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

[Feature request] Enable running without volume #570

Open
pbygrave-lucid opened this issue Dec 30, 2024 · 1 comment
Open

[Feature request] Enable running without volume #570

pbygrave-lucid opened this issue Dec 30, 2024 · 1 comment

Comments

@pbygrave-lucid
Copy link

pbygrave-lucid commented Dec 30, 2024

Hi Team,

Would it be worth looking at a way to run the helm-dashboard without volume storage? I get that we can already disable persistent storage but in my org we run our K8s clusters without any kind of volumes at all, meaning right now I cannot install the dashboard despite it's potential advantages in our environment.

If possible I'd like to understand what data the volume is being used to store and whether we may be able to utilise an alternative storage model, perhaps something AWS-backed like S3 if not just using normal container storage?

@pbygrave-lucid pbygrave-lucid changed the title Feature request: Enable running without volume [Feature request] Enable running without volume Dec 30, 2024
@undera
Copy link
Collaborator

undera commented Jan 4, 2025

Hi
The storage is used by Helm for its cache, downloads, repository indexes. We just set env variables (https://github.com/komodorio/helm-dashboard/blob/main/charts/helm-dashboard/templates/deployment.yaml#L40) and Helm code picks it up.

IMO it can work without volume at all, just it won't remember anything between container restarts.

If you are Helm-proficient, you might contribute the change that would respect existing persistence.enabled flag to disable volume storage completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants