argoproj / argoproj/argo-workflows
Passing k8s secret to a workflow as input
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
I know it is possible to pass a secret to a container via ENV or FILE. but it is not possible to pass it as an argument of a workflow.
# Use Cases
I have a few tools which accept values as command line args. These args are values which I'm not convenient in putting in YAMLs as plaintext and would like to store as k8s secrets.
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing how workflow arguments are resolved and how Kubernetes secrets are exposed to containers; done means a secret-backed value can be accepted as a workflow argument without plaintext in YAML, with coverage for the requested use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100