-
Notifications
You must be signed in to change notification settings - Fork 4.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
Remove support for Kubenet with containerd #10501
Merged
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
hakman:remove-kubenet-containerd
Dec 27, 2020
Merged
Remove support for Kubenet with containerd #10501
k8s-ci-robot
merged 1 commit into
kubernetes:master
from
hakman:remove-kubenet-containerd
Dec 27, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
labels
Dec 27, 2020
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
k8s-ci-robot
added
area/nodeup
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
labels
Dec 27, 2020
hakman
force-pushed
the
remove-kubenet-containerd
branch
from
December 27, 2020 12:57
dafcf1a
to
4c8ae0b
Compare
k8s-ci-robot
added
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
and removed
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
labels
Dec 27, 2020
hakman
force-pushed
the
remove-kubenet-containerd
branch
from
December 27, 2020 13:10
4c8ae0b
to
9f7a2e7
Compare
olemarkus
reviewed
Dec 27, 2020
hakman
force-pushed
the
remove-kubenet-containerd
branch
4 times, most recently
from
December 27, 2020 16:18
f92d0ea
to
2460bd9
Compare
hakman
force-pushed
the
remove-kubenet-containerd
branch
from
December 27, 2020 16:21
2460bd9
to
c02e5a2
Compare
/lgtm |
k8s-ci-robot
added
the
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
label
Dec 27, 2020
k8s-ci-robot
added a commit
that referenced
this pull request
Dec 28, 2020
…-upstream-release-1.19 Automated cherry pick of #10501: Remove support for Kubenet with containerd
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
area/api
area/nodeup
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
lgtm
"Looks good to me", indicates that a PR is ready to be merged.
size/L
Denotes a PR that changes 100-499 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kubenet is not actually supported for containerd and is unmaintained in general. Our current Kubenet setup for containerd is actually a "hack" that should be used only for development.
I had a longer discussion with some people involved in SIG-Networking and the recommendation is to remove this hack and also to stop using Kubenet in general (especially not as a default).