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

feat(open-webui): Add workload.kind configuration option for Deployment vs StatefulSet #109

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

Originally created by @lewisco on GitHub (Dec 15, 2025).

Feature Request

Description

Add a workload.kind configuration option to the open-webui Helm chart that allows users to explicitly choose between Deployment and StatefulSet workload types.

Use Case

When running Open WebUI with external storage (e.g., S3/MinIO for uploads, external PostgreSQL for data), a Deployment is often preferred over a StatefulSet because:

  • Easier horizontal scaling without PVC constraints
  • Simpler rollout/rollback behavior
  • No need for stable network identities when state is externalized
  • Better alignment with cloud-native stateless patterns

Currently, the chart uses StatefulSet only when persistence is enabled, but users may want a Deployment even with persistence disabled, or need finer control over this behavior.

Proposed Solution

Add a workload.kind value that accepts Deployment or StatefulSet, allowing explicit control over the workload type regardless of other settings.

Implementation

A PR implementing this feature is available: #325

Related:

Originally created by @lewisco on GitHub (Dec 15, 2025). ## Feature Request ### Description Add a `workload.kind` configuration option to the open-webui Helm chart that allows users to explicitly choose between `Deployment` and `StatefulSet` workload types. ### Use Case When running Open WebUI with external storage (e.g., S3/MinIO for uploads, external PostgreSQL for data), a `Deployment` is often preferred over a `StatefulSet` because: - Easier horizontal scaling without PVC constraints - Simpler rollout/rollback behavior - No need for stable network identities when state is externalized - Better alignment with cloud-native stateless patterns Currently, the chart uses StatefulSet only when persistence is enabled, but users may want a Deployment even with persistence disabled, or need finer control over this behavior. ### Proposed Solution Add a `workload.kind` value that accepts `Deployment` or `StatefulSet`, allowing explicit control over the workload type regardless of other settings. ### Implementation A PR implementing this feature is available: #325 --- **Related:** - PR: #325
yindo closed this issue 2026-02-15 19:16:23 -05:00
yindo commented 2026-02-15 19:16:23 -05:00
Author
Owner
Copy Link
Copy Source

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

Closed via https://github.com/open-webui/helm-charts/pull/325

@westbrook-ai commented on GitHub (Jan 1, 2026): Closed via https://github.com/open-webui/helm-charts/pull/325
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#109
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?