stackabletech / stackabletech/secret-operator
k8sSearch: duplicate scopes override rather than replace each other
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Affected version
23.7
Current and expected behavior
When declaring a secret volume with the scope service=foo,service=bar, secret-op will currently search for a secret with the label secrets.stackable.tech/service=bar, forgetting about service=foo entirely.
Secret-op should endeavour find a secret with both scopes.
Possible solution
Secret-op could query for a comma-separated list of services, such as secrets.stackable.tech/service=foo,bar.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
Contributor guide
No contributing guide indexed for this repository
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 at the k8sSearch entry point and trace how repeated service scopes are converted into secret label queries. Reproduce the service=foo,service=bar case, then verify that the search requires both scopes rather than discarding the first one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100