Add KEP for CNI traffic shaping support

[Lion-Wei]

Add KEP for CNI traffic shaping support.

Much of the meat in the KEP was taken from the original proposal.
(#1893)

We have been discussed about this proposal for a while, and already have a pr for basic realization:
kubernetes/kubernetes#63194

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: dcbw

Assign the PR to them by writing /assign @dcbw in a comment when ready.

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:

• keps/sig-network/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Lion-Wei]

/sig network
/assign @thockin @m1093782566
/cc @dcbw @squeed @caseydavenport @jingax10 @freehan @bowei
I think you maybe interested in this KEP, Please take a look, thanks, any advise or suggestion would be appreciated. : )

[k8s-ci-robot]

@Lion-Wei: GitHub didn't allow me to request PR reviews from the following users: squeed.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/sig network
/assign @thockin @m1093782566
/cc @dcbw @squeed @caseydavenport @jingax10 @freehan @bowei

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.

[Lion-Wei]

@haibinxie PTAL 😁

[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

[justaugustus]

/kind kep

[justaugustus]

/remove-lifecycle rotten

[justaugustus]

REMINDER: KEPs are moving to k/enhancements on November 30. Please attempt to merge this KEP before then to signal consensus.
For more details on this change, review this thread.

Any questions regarding this move should be directed to that thread and not asked on GitHub.

[justaugustus]

KEPs have moved to k/enhancements.
This PR will be closed and any additional changes to this KEP should be submitted to k/enhancements.
For more details on this change, review this thread.

Any questions regarding this move should be directed to that thread and not asked on GitHub.
/close

[k8s-ci-robot]

@justaugustus: Closed this PR.

In response to this:

KEPs have moved to k/enhancements.
This PR will be closed and any additional changes to this KEP should be submitted to k/enhancements.
For more details on this change, review this thread.

Any questions regarding this move should be directed to that thread and not asked on GitHub.
/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.

[uablrek]

@thockin It looks like this KEP was never moved to k/enhancements. So there is no tracking for this function and it has been left in alpha/experimental for >3 years. How to proceed? Kan I make a PR to add it as-is to k/enhancements?

[thockin]

You can bring it to k/enhancements, sure. The KEP template has evolved some, but sure. With the caveat that we're trying to finish a bunch of in-flight work before actively staring new debates :)

[uablrek]

But this one has been in-flight for 3 years, but unfortunately in "stealth mode".