-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Revert "Don't register the kubeletconfig group with the default Scheme" #51008
Conversation
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shyamjvs, wojtek-t Associated issue: 50789 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 |
@shyamjvs - how is it possible that presubmit didn't catch it? |
Good question - trying to figure out. |
@shyamjvs: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/test pull-kubernetes-e2e-gce-etcd3 |
All presubmits except kubemark are passing. Merging this manually to unblock submit-queue. |
Btw - the kubemark presubmit here failed due to a different reason:
@kubernetes/test-infra-maintainers This is affecting more and more PRs now. |
As @wojtek-t pointed out, some of the networks were leaked. I looked into it, and the runs 46434-46439 of the pr-kubemark job all failed to delete network due to undeleted minion still using it. I'm now manually cleaning it up. |
…scheme Automatic merge from submit-queue (batch tested with PRs 50967, 50505, 50706, 51033, 51028) Revert "Merge pull request #51008 from kubernetes/revert-50789-fix-scheme" I'm spinning up a cluster right now to test this fix, but I'm pretty sure this was the problem. There doesn't seem to be a way to confirm from logs, because AFAICT the logs from the hollow kubelet containers are not collected as part of the kubemark test. **What this PR does / why we need it**: This reverts commit f4afdec, reversing changes made to e633a16. This also fixes a bug where Kubemark was still using the core api scheme to manipulate the Kubelet's types, which was the cause of the initial revert. **Which issue this PR fixes**: fixes #51007 **Release note**: ```release-note NONE ``` /cc @shyamjvs @wojtek-t
Reverts #50789
To unblock SQ - #51007
cc @mtaufen