Support for Azure KeyVault and equivalent
Open
Nobody has claimed this yet.
kind/feature
needs-actor
priority/backlog
triage-accepted
- Dominant language
- Go
- Stars
- 331
- Forks
- 40
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 70
Description
The current examples contain placeholders for tokens and secrets in yaml files. It would be more secure to retrieve them from Azure KeyVault or equivalent via an External Secret Operator.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current YAML examples that contain token and secret placeholders, then investigate how Azure KeyVault or an equivalent External Secret Operator would fit their deployment flow. Done means the examples retrieve those values through the selected secret-management integration instead of storing placeholders, with the supported approach documented and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- cloud, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100