openshift / openshift/cloud-credential-operator
RFE: Allow specifying annotations/labels for Secrets created by operator
Open
Nobody has claimed this yet.
lifecycle/frozen
- Dominant language
- Go
- Stars
- 75
- Forks
- 196
- Avg merge
- 8d 13h
- Merged PRs (30d)
- 5
Description
In various cases, it would be helpful to allow specifying annotations/labels for the Secrets created by the 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
No files, tests, or entry points are named. Start by locating the operator paths that create Secrets and the relevant Kubernetes CRDs, then determine how users should provide annotations and labels and which Secret-creation cases must support them; done means the behavior is specified and covered for the requested cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100