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 #281] [MERGED] feat: allow to use existing ServiceAccount #300

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

📋 Pull Request Information

Original PR: https://github.com/open-webui/helm-charts/pull/281
Author: @AntonShadrinNN
Created: 8/6/2025
Status: ✅ Merged
Merged: 10/18/2025
Merged by: @westbrook-ai

Base: main ← Head: ashadrin/allow_not_to_create_sa

📝 Commits (3)

  • 010a20b feat: allow to use existing ServiceAccount
  • d56c7ce merge main
  • b565ff8 chore: merge main, fix docs, version updates

📊 Changes

8 files changed (+18 additions, -10 deletions)

View changed files

📝 charts/open-webui/Chart.yaml (+1 -1)
📝 charts/open-webui/README.md (+3 -2)
📝 charts/open-webui/templates/service-account.yaml (+1 -1)
📝 charts/open-webui/values.yaml (+5 -2)
📝 charts/pipelines/Chart.yaml (+1 -1)
📝 charts/pipelines/README.md (+4 -2)
📝 charts/pipelines/templates/service-account.yaml (+1 -1)
📝 charts/pipelines/values.yaml (+2 -0)

📄 Description

Closes #280

Introduces an additional ServiceAccount.create field for charts so that you can use an existing ServiceAccount without creating a new one. This solves the problem when utilities such as Vault Injector or Vault Secrets Webhook require one ServiceAccount per namespace.

🔄 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/281 **Author:** [@AntonShadrinNN](https://github.com/AntonShadrinNN) **Created:** 8/6/2025 **Status:** ✅ Merged **Merged:** 10/18/2025 **Merged by:** [@westbrook-ai](https://github.com/westbrook-ai) **Base:** `main` ← **Head:** `ashadrin/allow_not_to_create_sa` --- ### 📝 Commits (3) - [`010a20b`](https://github.com/open-webui/helm-charts/commit/010a20bc3bc646f8738588bd4060d4e007f82970) feat: allow to use existing ServiceAccount - [`d56c7ce`](https://github.com/open-webui/helm-charts/commit/d56c7ce3a2a8de6f4f83294111232993ca6d124c) merge main - [`b565ff8`](https://github.com/open-webui/helm-charts/commit/b565ff8d8faa81b87af684973ad6ec348a4d0e72) chore: merge main, fix docs, version updates ### 📊 Changes **8 files changed** (+18 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `charts/open-webui/Chart.yaml` (+1 -1) 📝 `charts/open-webui/README.md` (+3 -2) 📝 `charts/open-webui/templates/service-account.yaml` (+1 -1) 📝 `charts/open-webui/values.yaml` (+5 -2) 📝 `charts/pipelines/Chart.yaml` (+1 -1) 📝 `charts/pipelines/README.md` (+4 -2) 📝 `charts/pipelines/templates/service-account.yaml` (+1 -1) 📝 `charts/pipelines/values.yaml` (+2 -0) </details> ### 📄 Description Closes #280 Introduces an additional ServiceAccount.create field for charts so that you can use an existing ServiceAccount without creating a new one. This solves the problem when utilities such as Vault Injector or Vault Secrets Webhook require one ServiceAccount per namespace. --- <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:16 -05:00
yindo closed this issue 2026-02-15 19:17:16 -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#300
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?