stackabletech / stackabletech/secret-operator
k8sSearch scheduling errors don't report the failing query
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Rust
- Stars
- 13
- Forks
- 8
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Affected version
23.7
Current and expected behavior
The error message doesn't tell the user how they can fix the issue, or what the secrets' labels should be.
Possible solution
No response
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
Locate the k8sSearch scheduling error handling and inspect how the failing query and secret labels are currently represented in the error. Reproduce the scheduling failure to determine the information users need; done means the error explains the failure and how the secret labels should be configured.
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
- Needs clarification
- Newbie friendliness
- 25/100