open-webui/helm-charts
1
0
Fork 0
mirror of https://github.com/open-webui/helm-charts.git synced 2026-07-22 09:55:25 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Support external backing database to replace SQLite #73

New Issue
Closed
opened 2026-02-15 19:15:59 -05:00 by yindo · 2 comments
yindo commented 2026-02-15 19:15:59 -05:00
Owner
Copy Link
Copy Source

Originally created by @westbrook-ai on GitHub (Mar 11, 2025).

Open WebUI defaults to using a SQLite database stored in the backend for users, chats, and most other data. This does not scale well on Kubernetes, so we should explore a way to easily integrate an external database for scalability.

Originally created by @westbrook-ai on GitHub (Mar 11, 2025). Open WebUI defaults to using a SQLite database stored in the backend for users, chats, and most other data. This does not scale well on Kubernetes, so we should explore a way to easily integrate an external database for scalability.
yindo added the enhancement label 2026-02-15 19:15:59 -05:00
yindo closed this issue 2026-02-15 19:15:59 -05:00
yindo commented 2026-02-15 19:16:00 -05:00
Author
Owner
Copy Link
Copy Source

@westbrook-ai commented on GitHub (Oct 18, 2025):

There are a few issues with this:

  1. We would have to decide on the user's behalf which DB engine to use (Postgres, etc.)
  2. With the retirement of Bitnami charts, there are less well-maintained DB subchart options available
  3. Many DB engines make use of an Operator on K8s to maintain the DB deployment, which is not easily integrated into our chart, would be better as a technical how-to document

With these considerations in mind, I am closing this out.

@westbrook-ai commented on GitHub (Oct 18, 2025): There are a few issues with this: 1. We would have to decide on the user's behalf which DB engine to use (Postgres, etc.) 2. With the retirement of Bitnami charts, there are less well-maintained DB subchart options available 3. Many DB engines make use of an Operator on K8s to maintain the DB deployment, which is not easily integrated into our chart, would be better as a technical how-to document With these considerations in mind, I am closing this out.
yindo commented 2026-02-15 19:16:00 -05:00
Author
Owner
Copy Link
Copy Source

@qdii commented on GitHub (Oct 28, 2025):

The 3 points listed above assume that a user wants the open-webui helm chart to create and run the database for them. But in my humble opinion this is much more than asked.

Having a way to specify an externally-run database through a URI like mariadb://user:password@hostname would be enough for most of us, and would allow us to decide the SQL flavor we'd like to use (e.g. postgres, mariadb).

@qdii commented on GitHub (Oct 28, 2025): The 3 points listed above assume that a user wants the open-webui helm chart to create and run the database for them. But in my humble opinion this is much more than asked. Having a way to specify an externally-run database through a URI like `mariadb://user:password@hostname` would be enough for most of us, and would allow us to decide the SQL flavor we'd like to use (e.g. postgres, mariadb).
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 enhancement
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#73
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?