open-webui/helm-charts
1
0
Fork 0
mirror of https://github.com/open-webui/helm-charts.git synced 2026-07-21 17:35:26 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Use persistence with kind deployment #57

New Issue
Open
opened 2026-02-15 19:15:50 -05:00 by yindo · 3 comments
yindo commented 2026-02-15 19:15:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @corey-kline on GitHub (Feb 4, 2025).

I want to use persistence, but I also want to use a deployment instead of a StatefulSet. Can this be done without causing issues? I'm happy to make the change myself, but assuming this was done intentionally, I'm wary of breaking some storage mechanism I don't have enough knowledge on.

I believe adding a values.controller.type equal to deployment or statefulSet and making this conditional based off that value would allow users to better customize their installation. To preserve compatibility we can leave it unset by default use a helper that falls back to the existing logic when unset.

Thanks!

Originally created by @corey-kline on GitHub (Feb 4, 2025). I want to use persistence, but I also want to use a deployment instead of a StatefulSet. Can this be done without causing issues? I'm happy to make the change myself, but assuming this was done intentionally, I'm wary of breaking some storage mechanism I don't have enough knowledge on. I believe adding a `values.controller.type` equal to `deployment` or `statefulSet` and making [this conditional](https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/templates/workload-manager.yaml#L2-L6) based off that value would allow users to better customize their installation. To preserve compatibility we can leave it unset by default use a helper that falls back to the existing logic when unset. Thanks!
yindo added the question label 2026-02-15 19:15:50 -05:00
yindo commented 2026-02-15 19:15:51 -05:00
Author
Owner
Copy Link
Copy Source

@westbrook-ai commented on GitHub (Feb 9, 2025):

Hi @corey-kline, the PR that initially submitted that configuration is here: https://github.com/open-webui/helm-charts/pull/36

From reading that PR, it sounds like the main reason that change was made was for multi-node deployments. I would be open to the changes you proposed if you find that using a Deployment instead of a StatefulSet with persistence enabled doesn't cause issues.

Feel free to tag me in a PR if you submit one, or in any further discussion here if you need some help verifying any findings. Thanks for submitting this!

@westbrook-ai commented on GitHub (Feb 9, 2025): Hi @corey-kline, the PR that initially submitted that configuration is here: https://github.com/open-webui/helm-charts/pull/36 From reading that PR, it sounds like the main reason that change was made was for multi-node deployments. I would be open to the changes you proposed if you find that using a Deployment instead of a StatefulSet with persistence enabled doesn't cause issues. Feel free to tag me in a PR if you submit one, or in any further discussion here if you need some help verifying any findings. Thanks for submitting this!
yindo commented 2026-02-15 19:15:51 -05:00
Author
Owner
Copy Link
Copy Source

@ncrmro commented on GitHub (Mar 11, 2025):

@0xThresh I think it would make sense to move to a deployment and instead use Postgres via the Bitnmai helm chart or Postgres Operator.

The Postgres Operator is bit more involved but supports high availability/failover, automated backups etc.

I can open a PR if you'd like

@ncrmro commented on GitHub (Mar 11, 2025): @0xThresh I think it would make sense to move to a deployment and instead use Postgres via the [Bitnmai helm chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql) or [Postgres Operator](https://access.crunchydata.com/documentation/postgres-operator/latest/installation/helm#installing-directly-from-the-registry). The Postgres Operator is bit more involved but supports high availability/failover, automated backups etc. I can open a PR if you'd like
yindo commented 2026-02-15 19:15:51 -05:00
Author
Owner
Copy Link
Copy Source

@westbrook-ai commented on GitHub (Mar 11, 2025):

Thanks @ncrmro, I'm open to the PR for moving to the deployment. I think the Postgres PR should be separate but I'm open to that as well since I've personally suffered the consequences of starting with the SQLite DB on K8s. I've opened https://github.com/open-webui/helm-charts/issues/200 to track those efforts.

@westbrook-ai commented on GitHub (Mar 11, 2025): Thanks @ncrmro, I'm open to the PR for moving to the deployment. I think the Postgres PR should be separate but I'm open to that as well since I've personally suffered the consequences of starting with the SQLite DB on K8s. I've opened https://github.com/open-webui/helm-charts/issues/200 to track those efforts.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
awaiting-user-feedback
awaiting-user-feedback
bug
bug
documentation
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
upstream
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: open-webui/helm-charts#57
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?