-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
WIP - speculative revert of 1599 #1647
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: liggitt The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold not really intending to merge this unless it magically cleans up all our CI signal |
/test all |
failed, but with timeout startup errors (resource exhaustion?), not the predominant pod kill errors? /retest |
/test pull-kind-e2e-kubernetes |
/test pull-kind-e2e-kubernetes |
FYI @dims this mostly seems to be a containerd rollback. The kind base image tag has Sha in it, https://github.com/containerd/containerd/compare/1e902b2d..449e9269 :/ |
https://github.com/kubernetes-sigs/kind/compare/21e528f5..fd490400#diff-424162915c2ab4ab7f1b3f6dff73946e looks interesting, especially with the error we're seeing in on the failed pods:
|
oh, that just got merged two days ago in #1639 ... it isn't the culprit |
/test all |
/test pull-kind-e2e-kubernetes |
6 e2e runs without pod kill issues ... |
more runs coming in #1649 w/ new images |
Closing in favor of #1649 |
Just to exercise CI... seeing close to 100% failure rates on kubernetes/kubernetes#91579 on master
the containerd diff brought in fifo/logging/process killing changes, which might be related to kubernetes/kubernetes#91579
cc @BenTheElder