Feature Request: Make OpenBao a default Secrets backend #284
Labels
No labels
🐛 bug
DO THE THING >:(
blocked
dependencies
k3s
kind
openbao
question
secrets
wontfix
✨ enhancement
🌱good first issue
📓documentation
📕kyverno
🔐 Bitwarden
🙋help wanted
🦩 MinIO
🧸 🧸 Duplicate
🩹 Bug Fix
🪠 CICD
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
small-hack/smol-k8s-lab#284
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Describe the feature you'd like, and why
I want to offer official support of OpenBao as the primary secrets backend, instead of using Bitwarden. I still want to have Bitwarden as an option, because it's useful for smaller home labs, but OpenBao would give us the power to more comfortably separate sensitive infra data from a personal password manager.
Describe alternatives you've considered, if any
We want will also support Vault, but it would be a secondary less supported option, because Vault, along with Hashicorp is now owned by IBM, and we remember what happened with centos.
Additional context
We'll need to make sure the Argo CD app, small-hack/argocd-apps:demo/openbao works and graduate it out of demo.
We need to test the new external secrets provider with each major app that uses bitwarden right now:
We've add OpenBao as a default demo app here: https://github.com/small-hack/smol-k8s-lab/pull/286
#290 helps a bit with our goals here as it makes Bitwarden optional for our ArgoCD object :)