Migrate kubenet bells and whistles to cni

[freehan]

Stuff to migrate:

1. sysctl bridge-nf-call-iptables
2. promiscuous bridge mode and ebtables deduplication
3. traffic shaper
4. hostport

[cmluciano]

@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

[thockin]

@dnardo probably a dup of other(s)

[dnardo]

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)
#4 is being handled in another PR in the CNI repo.

I don't know of any dup issues, I'll take a look and I close any dups.

[cmluciano]

/assign @dnardo

[k8s-ci-robot]

@cmluciano: GitHub didn't allow me to assign the following users: dnardo.

Note that only kubernetes members can be assigned.

In response to this:

/assign @dnardo

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.

[cmluciano]

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

[dnardo]

/assign

[dnardo]

/assign @bowei

[dnardo]

/unassign @bowei

[thockin]

This seems unlikely for 1.7?

[freehan]

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.

[luxas]

@freehan Will that upcoming new (splitted-up) release be called v0.6.0?

[freehan]

@luxas I am not sure.
@dcbw comment?

[feiskyer]

@freehan Seems there is still no clear plan of this? e.g. in which release kubenet will be deprecated?

[m1093782566]

There is a proposal on Support traffic shaping for CNI network plugin, which is intended to fix "traffic shaper", please check it out.

Thanks!

[fejta-bot]

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.
/lifecycle stale

[bboreham]

/remove-lifecycle stale

[fejta-bot]

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.
/lifecycle stale

[thockin]

/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> .

[bowei]

/assign @jingax10

[jellonek]

so what is the status of this issue?

[luxas]

ping @kubernetes/sig-network-feature-requests

[cmluciano]

@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.

[caseydavenport]

@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.

[athenabot]

@m1093782566 @dnardo @jingax10
If this issue has been triaged, please comment /remove-triage unresolved.

If you aren't able to handle this issue, consider unassigning yourself and/or adding the help-wanted label.

🤖 I am a bot run by vllry. 👩‍🔬

[fejta-bot]

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.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.