Add better secret support
- Dominant language
- Shell
- Stars
- 62
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
**Is this a request for help?**: No
---
**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): Feature Request
Add support for different secrets like S3 credentials for non AWS platforms and document ways to retrieve them in pipelines (normal steps and docker plugin steps).
If I understand the current code correctly, only a handful of custom settings are currently stored as k8s secrets.
Other secrets can only be added as ENV vars.
Ideally you could add all kind of different vars as secrets to k8s.
Additionally, it would be helpful for beginners to document, how to utilize the k8s secret store in pipelines.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how the chart currently stores custom settings as Kubernetes secrets and how pipeline configuration is documented. Done means supporting arbitrary variables such as S3 credentials as Kubernetes secrets and documenting retrieval in normal pipeline steps and Docker plugin steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, documentation, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100