-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Clean up event messages for errors. #89794
Conversation
/priority important-soon |
cc: @kubernetes/release-managers |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: msau42, saad-ali The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Change-Id: Ib70b50e676b917c4d976f32ee7a19f8fc63b6bc6
/lgtm |
…-upstream-release-1.18 Automated cherry pick of #89794: Clean up event messages for errors.
…-upstream-release-1.17 Automated cherry pick of #89794: Clean up event messages for errors.
…-upstream-release-1.16 Automated cherry pick of #89794: Clean up event messages for errors.
…-upstream-release-1.15 Automated cherry pick of #89794: Clean up event messages for errors.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Error output from some volume clients can be quite verbose. These messages currently propagate to Kubernetes events, which causes a bit of event spam. This change leaves the details to logs instead, and keeps the event message short.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: