-
Notifications
You must be signed in to change notification settings - Fork 42.3k
Upgrade klog to avoid panics crashing components #100156
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
Conversation
|
please use klog |
|
/sig node FYI |
|
/milestone v1.21 (since this is a critical fix) |
|
Need ./hack/update-internal-modules.sh ? |
|
flake #99801 |
|
/triage accepted |
|
/approve |
|
/assign @liggitt |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, ehashman, liggitt, pacoxu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Looks like: /test pull-kubernetes-e2e-kind |
What type of PR is this?
/kind bug
/kind flake
/priority critical-urgent
What this PR does / why we need it:
Upgrades klog to pull in critical bugfixes.
Which issue(s) this PR fixes:
Fixes #100155 and #98976 (comment). These are the only two changes in the vendor diff.
Special notes for your reviewer:
Waiting on a klog release, testing this against HEAD for now.Upgraded to klog v2.8.0.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @dims @serathius @pacoxu