-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: print error message in message field inside status in rollouts … #3932
base: master
Are you sure you want to change the base?
Conversation
Published E2E Test Results 4 files 4 suites 5h 12m 13s ⏱️ For more details on these failures, see this check. Results for commit 0af3b0a. ♻️ This comment has been updated with latest results. |
Published Unit Test Results2 307 tests 2 307 ✅ 2m 59s ⏱️ Results for commit 0af3b0a. ♻️ This comment has been updated with latest results. |
|
…object Signed-off-by: Abhishek Bansal <[email protected]>
Signed-off-by: Abhishek Bansal <[email protected]>
Signed-off-by: Abhishek Bansal <[email protected]>
21827ac
to
a16701f
Compare
@zachaller could you please provide some help to resolve the failures on end to end testing ? |
|
Enhancement: Improved Error Reporting in Rollouts Controller
This PR introduces an enhancement to the rollouts controller, allowing it to record reconciliation error messages directly in the status field of Rollout objects.
Benefits:
Enhanced User Experience: Users can now view error messages associated with a Rollout object directly in its status, eliminating the need to search through the controller logs for debugging purposes.
Faster Issue Resolution: By surfacing errors in the status field, users can identify and address issues more efficiently, streamlining the troubleshooting process.
This enhancement is aimed at improving the overall usability and developer experience while working with Rollout objects.
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.