ironcore-dev / ironcore-dev/boot-operator
Add ErrorMessage field to CR status for better troubleshooting
Open
Nobody has claimed this yet.
area/metal-automation
- Dominant language
- Go
- Stars
- 6
- Forks
- 9
- Avg merge
- 19h 5m
- Merged PRs (30d)
- 10
Description
What would you like to be added: Add an ErrorMessage field in the CR status to make it easier to understand what went wrong without checking logs.
Why is this needed: Improves troubleshooting and overall status clarity.
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
Start by locating the custom resource status definition and the controller paths that update status. Check existing status-related tests, if present, before deciding where the ErrorMessage value should be populated. Done means the CR status exposes a useful error message for troubleshooting and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100