-
Notifications
You must be signed in to change notification settings - Fork 38.8k
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
remove stale OutOfDisk condition from kubelet side #72507
Conversation
bcbfb89
to
7f72bac
Compare
LGTM |
/retest |
/test pull-kubernetes-local-e2e-containerized |
1 similar comment
/test pull-kubernetes-local-e2e-containerized |
7f72bac
to
b0343ef
Compare
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.
We do need a test to verify the change @dixudx
b0343ef
to
e1a854b
Compare
Flaky tests here. Will retest it when the CI becomes happy. |
looks good to me structurally will leave to @kubernetes/sig-node-pr-reviews for lgtm/approval |
/lgtm |
/retest |
1 similar comment
/retest |
ping @kubernetes/sig-node-pr-reviews for approval. Thanks. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dixudx, yujuhong 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 |
/priority important-soon |
References: - gardener/machine-controller-manager#214 - kubernetes/kubernetes#72507 ```improvement operator The shoot care controller does now remove stale `OutOfDisk` node conditions for 1.13 clusters. See kubernetes/kubernetes#72507 for more details. ```
…507-upstream-release-1.13 Automated cherry pick of #72507: remove stale OutOfDisk condition from kubelet side
What type of PR is this?
Remove stale node condition OutOfDisk
What this PR does / why we need it:
Node condition OutOfDisk has been removed starting from v1.13
A 1.12 kubelet upgraded to a 1.13 kubelet leaves the previously reported OutOfDisk condition in place, and it eventually gets switched to Unknown status.
We should cherry pick this to v1.13.
Which issue(s) this PR fixes:
Fixes #72485
Special notes for your reviewer:
/cc liggitt resouer
/cc kubernetes/sig-node-bugs
Does this PR introduce a user-facing change?:
Signed-off-by: stephen.xd@alibaba-inc.com