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
Migrate kubenet bells and whistles to cni #38890
Comments
@freehan Does that mean moving to https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/network/cni/cni.go ? I think I can accomplish 1) in tandem with #26005 |
@dnardo probably a dup of other(s) |
Although I cannot assign myself to this, I'm currently working on this. #2 is pending merge in the CNI repo. I have code ready for #1 and #3 (however we may need further discussion on #3 since it requires that the traffic shaper "knows" the pod IP on deletion, and right now we have no good way to do this in CNI) I don't know of any dup issues, I'll take a look and I close any dups. |
/assign @dnardo |
@cmluciano: GitHub didn't allow me to assign the following users: dnardo. Note that only kubernetes members can be assigned. In response to this:
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. |
I'll assign this to myself tracking @dnardo. I think you send an email to the contrib-X SIG requesting member access to the kubernetes repo. /assign |
/assign |
/assign @bowei |
/unassign @bowei |
This seems unlikely for 1.7? |
Revendoring the CNI plugins is pending on a new CNI release. Because CNI just went thru a separation between plugins and libcni, and there is no release tag in plugin repo. |
@freehan Will that upcoming new (splitted-up) release be called v0.6.0? |
@freehan Seems there is still no clear plan of this? e.g. in which release kubenet will be deprecated? |
There is a proposal on Support traffic shaping for CNI network plugin, which is intended to fix "traffic shaper", please check it out. Thanks! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale
…On Sun, Sep 2, 2018, 3:07 AM fejta-bot ***@***.***> wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
<https://github.com/fejta>.
/lifecycle stale
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38890 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVCqYr5Vpf-EsjHHFVN9-pMmLAOvHks5uW63kgaJpZM4LPhLb>
.
|
/assign @jingax10 |
so what is the status of this issue? |
ping @kubernetes/sig-network-feature-requests |
@caseydavenport @jingax10 @bowei I think we briefly discussed this at the Kubecon SIG Net meetup, but I do not recall what we determined were the missing features left. |
@cmluciano I think it's mostly just a packaging issue IIRC. AFAIK we should be able to get feature parity with an external bridge/ptp/host-local CNI plugin configuration at this point. |
@m1093782566 @dnardo @jingax10 If you aren't able to handle this issue, consider unassigning yourself and/or adding the 🤖 I am a bot run by vllry. 👩🔬 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
Stuff to migrate:
The text was updated successfully, but these errors were encountered: