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

[PR #260] [MERGED] Support for setting both s3 keys from existing secret #287

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

📋 Pull Request Information

Original PR: https://github.com/open-webui/helm-charts/pull/260
Author: @cableman
Created: 7/7/2025
Status: ✅ Merged
Merged: 7/15/2025
Merged by: @westbrook-ai

Base: main ← Head: feature/s3-secret

📝 Commits (1)

  • f0c4ec1 Added support for setting both s3 keys from existing secret

📊 Changes

2 files changed (+15 additions, -2 deletions)

View changed files

📝 charts/open-webui/templates/workload-manager.yaml (+8 -1)
📝 charts/open-webui/values.yaml (+7 -1)

📄 Description

If you are using CEPH S3 storage in Kubernetes you get a secret with both accessKey and secretKey. So being able to reuse that secret for setting S3 storage, will make things easier.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/helm-charts/pull/260 **Author:** [@cableman](https://github.com/cableman) **Created:** 7/7/2025 **Status:** ✅ Merged **Merged:** 7/15/2025 **Merged by:** [@westbrook-ai](https://github.com/westbrook-ai) **Base:** `main` ← **Head:** `feature/s3-secret` --- ### 📝 Commits (1) - [`f0c4ec1`](https://github.com/open-webui/helm-charts/commit/f0c4ec17836888b0dc0237e379df149eb85f23d6) Added support for setting both s3 keys from existing secret ### 📊 Changes **2 files changed** (+15 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `charts/open-webui/templates/workload-manager.yaml` (+8 -1) 📝 `charts/open-webui/values.yaml` (+7 -1) </details> ### 📄 Description If you are using CEPH S3 storage in Kubernetes you get a secret with both accessKey and secretKey. So being able to reuse that secret for setting S3 storage, will make things easier. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 19:17:13 -05:00
yindo closed this issue 2026-02-15 19:17:13 -05:00
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 pull-request
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#287
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?