-
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
network/cni: Bring up the lo
interface for rkt
#29310
Conversation
I'd also like to suggest this as a cherry-pick candidate and possibly re-title to clarify that it ends up impacting rkt+cni and making it a release note / bugfix. |
LGTM. Would be useful for openshift/origin#9981 too since I hard-coded the same thing there (though not with the CNI 'lo' plugin). |
"name": "cni-loopback", | ||
"type": "loopback" | ||
}`)) | ||
if err != nil { |
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.
nit: would the error be caused by other things like oom? Though it should be pretty rare.
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.
OOm should not manifest as an error ever.
LGTM |
Though frankly the vendor dir thing should probably be removed in a followup PR.
Removing label |
@dcbw you should have enough authority to apply the lgtm label here. You are fully authorized to approve changes like this - you are as much an owner of this code as anyone. |
GCE e2e build/test passed for commit 6aed2a0. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 6aed2a0. |
Automatic merge from submit-queue |
backport of kubernetes#29310 See issue kubernetes#28561
backport of: kubernetes#29310 Though frankly the vendor dir thing should probably be removed in a followup PR.
@euank Cherrypick approved. Please create a cherrypick PR. Thanks. |
lo
interfacelo
interface for rkt
Can we swap the label here to "release-note"? I re-titled it to something that I think accurately conveys the bugfix. |
backport of kubernetes#29310 See issue kubernetes#28561
backport of: kubernetes#29310 Though frankly the vendor dir thing should probably be removed in a followup PR.
Commit found in the "release-1.3" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
…of-#29310-upstream-release-1.3 Automatic merge from submit-queue Automated cherry pick of kubernetes#29310 Cherry pick of kubernetes#29310 on release-1.3.
…of-#29310-upstream-release-1.3 Automatic merge from submit-queue Automated cherry pick of kubernetes#29310 Cherry pick of kubernetes#29310 on release-1.3.
This is already done in kubenet. This specifically fixes an issue where a kubelet-managed network for the rkt runtime does not have an "UP" lo interface.
Fixes #28561
If this fix doesn't seem right, it could also be implemented by rkt effectively managing two "cni" network plugins, one for the user requested network, one for lo.
Followup CRs can improve unit testing further and then possibly remove the vendor directory logic (which seems like dead code)
cc @kubernetes/sig-rktnetes @kubernetes/sig-network @dcbw