[GH-ISSUE #152] Use persistence with kind deployment #57

New issue

Closed

opened 2026-10-18 21:05:17 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-18 21:05:17 +00:00

Owner

Originally created by @corey-kline on GitHub (Feb 5, 2025).
Original GitHub issue: https://github.com/open-webui/helm-charts/issues/152

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 5, 2025). Original GitHub issue: https://github.com/open-webui/helm-charts/issues/152 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!

bsakaguchi

2026-10-18 21:05:17 +00:00

closed this issue
added the
question
label

bsakaguchi commented

2026-10-18 21:05:19 +00:00

Author

Owner

@james-westbrook 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!

@james-westbrook 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!

bsakaguchi commented

2026-10-18 21:05:19 +00:00

Author

Owner

@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

bsakaguchi commented

2026-10-18 21:05:19 +00:00

Author

Owner

@james-westbrook commented on GitHub (Mar 12, 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.

@james-westbrook commented on GitHub (Mar 12, 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.

bsakaguchi commented

2026-10-18 21:05:19 +00:00

Author

Owner

@james-westbrook commented on GitHub (Apr 9, 2026):

This is now supported via the workload.kind value.

@james-westbrook commented on GitHub (Apr 9, 2026): This is now supported via the `workload.kind` value.

bsakaguchi referenced this issue

2026-10-18 21:06:55 +00:00

[PR #57] [MERGED] Upgrade Chart Dependencies #172