-
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
Update cadvisor godeps to v0.28.3 #56967
Update cadvisor godeps to v0.28.3 #56967
Conversation
/ok-to-test |
This godep update contains three changes in total:
All three changes are low risk by my assessment. /assign @dchen1107 @yujuhong |
/sig node |
/kind bug |
/priority critical-urgent |
/lgtm
This is a reliability fix and the main reason for bumping cadvisor version right now. |
We need to get this PR approved and merged today. It appears to relate to a serious issue, but we also need to close the 1.9 release train. Can a SIG lead look at this please? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, jsravn, yujuhong Associated issue: #53207 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
[MILESTONENOTIFIER] Milestone Pull Request Current Note: This pull request is marked as Example update:
Pull Request Labels
|
Automatic merge from submit-queue (batch tested with PRs 56599, 56824, 56918, 56967, 56959). If you want to cherry-pick this change to another branch, please follow the instructions here. |
Is this cherry pickable to 1.8? I started trying to do it, but the vendoring differences are relatively significant (cadvisor 2.7.3->2.8.3, which brings in dockerd->containerd change). Also finding the vendoring process really painstaking overall. So don't want to spend more time on it unless someone gives the okay for a cherry pick. Thanks! |
Update cadvisor dependency to v0.27.4. Fix kubernetes#53207.
…-upstream-release-1.8 Automatic merge from submit-queue. Cherry pick of #56967 to release-1.8 **What this PR does / why we need it**: Adds timeout around docker queries, to prevent wedging kubelet on node status updates if docker is non-responsive. **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes #53207 Cherry picks #56967 **Special notes for your reviewer**: Kubelet's node status update queries cadvisor, which had no timeout on underlying docker queries. As a result, if docker was non responsive, kubelet would never be able to recover itself without a restart. **Release note**: ```release-note Timeout docker queries to prevent node going NotReady indefinitely. ```
What this PR does / why we need it:
Adds timeout around docker queries, to prevent wedging kubelet on node status updates if docker is non-responsive.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #53207
Special notes for your reviewer:
Kubelet's node status update queries cadvisor, which had no timeout on underlying docker queries. As a result, if docker was non responsive, kubelet would never be able to recover itself without a restart.
Release note: