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

Is Helm chart the recommended deployment strategy for Kubernetes? #112

New Issue
Closed
opened 2026-02-15 19:16:23 -05:00 by yindo · 1 comment
yindo commented 2026-02-15 19:16:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @flobrunner on GitHub (Jan 12, 2026).

Description
I upgraded OWUI from 8.19.0 → 9.0.0 → 10.2.1 and noticed that a Redis dependency was introduced automatically, apparently for websockets, without prior indication or explicit configuration.

This caused unexpected changes in my Kubernetes setup and is problematic for production environments.

Could you clarify:

  • Is the Helm chart the officially recommended way to deploy OWUI on Kubernetes for production?
  • Are new mandatory dependencies (like Redis) expected to be introduced during upgrades?
  • Is the Redis requirement for websockets intentional and documented?
    (Related to issue #161)

A clear statement on the recommended production deployment and upgrade expectations would help avoid surprises in future releases.

Originally created by @flobrunner on GitHub (Jan 12, 2026). **Description** I upgraded OWUI from **8.19.0 → 9.0.0 → 10.2.1** and noticed that a **Redis dependency was introduced automatically**, apparently for websockets, without prior indication or explicit configuration. This caused unexpected changes in my Kubernetes setup and is problematic for production environments. Could you clarify: * Is the **Helm chart** the officially recommended way to deploy OWUI on Kubernetes for production? * Are **new mandatory dependencies** (like Redis) expected to be introduced during upgrades? * Is the Redis requirement for websockets intentional and documented? (Related to issue #161) A clear statement on the recommended production deployment and upgrade expectations would help avoid surprises in future releases.
yindo closed this issue 2026-02-15 19:16:23 -05:00
yindo commented 2026-02-15 19:16:24 -05:00
Author
Owner
Copy Link
Copy Source

@westbrook-ai commented on GitHub (Feb 1, 2026):

Hi @flobrunner,

  1. Yes, this is the supported way to deploy Open WebUI in production for Kubernetes, but note that this repo is maintained by volunteers and is admittedly not always perfect. We intentionally gated the websockets change behind MAJOR version releases due to the potential disruption that could be caused by introducing it.
  2. There may be times when mandatory new dependencies/ removed dependencies are necessary, but this is not something we would ever introduce in a minor version since most administrators expect to be able to roll out minor versions with no impact to their running workloads. This kind of change will always be done in a major version
  3. Yes. Without websockets, Open WebUI can have issues on multi-pod deployments, which you can read more about here: https://docs.openwebui.com/tutorials/integrations/redis#when-is-redis-required.

We definitely need to get better about our changelogs so that these changes are better documented, so thank you for the feedback. I will work on getting changelogs automated and included in every release in the near future so that it's obvious what changes can be expected between versions, which is especially important for our major version updates.

@westbrook-ai commented on GitHub (Feb 1, 2026): Hi @flobrunner, 1. Yes, this is the supported way to deploy Open WebUI in production for Kubernetes, **but note that this repo is maintained by volunteers** and is admittedly not always perfect. We intentionally gated the websockets change behind MAJOR version releases due to the potential disruption that could be caused by introducing it. 2. There may be times when mandatory new dependencies/ removed dependencies are necessary, but this is not something we would ever introduce in a minor version since most administrators expect to be able to roll out minor versions with no impact to their running workloads. This kind of change will always be done in a major version 3. Yes. Without websockets, Open WebUI can have issues on multi-pod deployments, which you can read more about here: https://docs.openwebui.com/tutorials/integrations/redis#when-is-redis-required. We definitely need to get better about our changelogs so that these changes are better documented, so thank you for the feedback. I will work on getting changelogs automated and included in every release in the near future so that it's obvious what changes can be expected between versions, which is especially important for our major version updates.
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
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#112
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?