SIG Network v1.22 targeted KEPs

[Casey Davenport]

Hey SIG network -

As mentioned on the call today, we have exactly two weeks to agree what KEPs we are targeting for Kubernetes v1.22. The process is slightly different this time (as described here) and we need to explicitly opt-in our enhancements by May 13 in order for them to be considered.

I am starting this thread as a means to collect the in-progress work for consideration for v1.22. If you have a KEP you would like considered, please reply-all to this email with a link to the KEP, targeted status for v1.22, and who the assignee/owner is (if not yourself!)

Also, please make sure any proposed enhancements are up to date!

We can discuss here on the mailing list, as well as on the next meeting, after which we'll finalize our submissions in the spreadsheet.

- Casey

[Casey Davenport]

Also please note that enhancement freeze is also Thursday May 13th, and all v1.22 KEPs must be merged and meet review requirements by 23:59:59 PST Tuesday 13th May. So make sure you're asking for reviews if you need them!

[Ricardo Katz]

So, my bigger question here is, we wanted to target endPort Kep for BETA in v1.22, but the graduation policy established (4 CNIs) does not seems to be covered until the freeze. I know Calico and Antrea are on their way to, but if we don't get other 2 CNIs to support this, should we wait until v1.23?

Thanks!

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-network" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-ne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/13a43fbb-a35a-44ee-919b-a76030c82d76n%40googlegroups.com.

[Swetha Repakula]

Hello!

I would like to add the EndpointSlice KEP for v1.22
KEP: https://github.com/kubernetes/enhancements/blob/54e4141b10537f5e009b26cb420b2d2a71c04b7e/keps/sig-network/0752-endpointslices/README.md

Enhancement Issue: https://github.com/kubernetes/enhancements/issues/752
Target Status for v1.22: Implemented
Assignee: Swetha (gh: swetharepakula)

The KEP requires a couple of updates/clarifications to reflect the changes that went into v1.21 but the changes targeted for v1.22 should not change.

Thanks!

Swetha

[Rob Scott]

Hey Everyone,

I've also got a few KEPs that I'd like to add to the 1.22 cycle

- Topology Aware Hints - Hoping to graduate to Beta

- Namespace-Scoped Ingress Class Params - Hoping to graduate to Beta

- AppProtocol - Can finally remove the feature gate in this cycle and close out the KEP

Thanks!

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/f059a111-96c4-4c8f-9589-b28ed882a328n%40googlegroups.com.

[Geon-Ju Kim]

I would like to add a new KEP Expanded DNS Configuration to the v1.22 cycle.

It's currently in the PRR stage, but I'd like to merge it by the enhancement freeze.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAGY4dknuZR8XGVWkTYhW%3Dj52EKxz%2BV58zgJ4Luz6ceLDEx%3DNsg%40mail.gmail.com.

[Ricardo Katz]

I would like to add Network Policy EndPort in tracking for beta graduation

Thanks!!

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAHtF6kBfDw1MeGdcYyLVmecPBjyEt15dWuO9TX1GDiD6taQT7Q%40mail.gmail.com.

[Tim Hockin]

On Thu, Apr 29, 2021 at 3:01 PM Ricardo Katz <ricard...@gmail.com> wrote:

So, my bigger question here is, we wanted to target endPort Kep for BETA in v1.22, but the graduation policy established (4 CNIs) does not seems to be covered until the freeze. I know Calico and Antrea are on their way to, but if we don't get other 2 CNIs to support this, should we wait until v1.23?

I note that both beta and GA say "four NetworkPolicy providers".

What 4 were you targeting?  Does it make sense for you to go try to implement or at least motivate the others?

I do think we should hold our criteria, but I could see adjusting this to 3 instead of 4 for beta.

 

Thanks!

On Thu, Apr 29, 2021 at 6:52 PM Casey Davenport <ca...@tigera.io> wrote:

Also please note that enhancement freeze is also Thursday May 13th, and all v1.22 KEPs must be merged and meet review requirements by 23:59:59 PST Tuesday 13th May. So make sure you're asking for reviews if you need them!

On Thursday, April 29, 2021 at 2:48:32 PM UTC-7 Casey Davenport wrote:

Hey SIG network -

As mentioned on the call today, we have exactly two weeks to agree what KEPs we are targeting for Kubernetes v1.22. The process is slightly different this time (as described here) and we need to explicitly opt-in our enhancements by May 13 in order for them to be considered.

I am starting this thread as a means to collect the in-progress work for consideration for v1.22. If you have a KEP you would like considered, please reply-all to this email with a link to the KEP, targeted status for v1.22, and who the assignee/owner is (if not yourself!)

Also, please make sure any proposed enhancements are up to date!

We can discuss here on the mailing list, as well as on the next meeting, after which we'll finalize our submissions in the spreadsheet.

- Casey

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-network" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-ne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/13a43fbb-a35a-44ee-919b-a76030c82d76n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-network" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-ne...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAG3fPQ7N0c5ekBP4ju1E9ok0oHYTO%2Byi%3DTnQM49O32t_z%3DkeNg%40mail.gmail.com.

[Tim Hockin]

Swetha - I added #752 to the sheet.

On Thu, Apr 29, 2021 at 6:10 PM 'Swetha Repakula' via kubernetes-sig-network <kubernetes-...@googlegroups.com> wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/f059a111-96c4-4c8f-9589-b28ed882a328n%40googlegroups.com.

[Tim Hockin]

Ricardo - I added this to the sheet

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAG3fPQ4zLqKUxgQ5RGpqS3F6q4L-OsWpG_xNFNmMyq6EU9DNdA%40mail.gmail.com.

[Tim Hockin]

Rob,

Your KEP enhancement issues need to be updated ;)

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAGY4dknuZR8XGVWkTYhW%3Dj52EKxz%2BV58zgJ4Luz6ceLDEx%3DNsg%40mail.gmail.com.

[Tim Hockin]

Geon-Ju: I added this to the sheet

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAHtF6kBfDw1MeGdcYyLVmecPBjyEt15dWuO9TX1GDiD6taQT7Q%40mail.gmail.com.

[Rob Scott]

I've got one more to add. We need to close out KEP 536 - the original Topology KEP. I'm happy to take that on, but if someone else is already on it, that's great too.

[Rob Scott]

Looking through other sig-network KEPs, there are a couple more missing from this thread. Not sure if Andrew or anyone else has time to move these forward in this cycle, but would love to get them tracked if so:

- KEP 1669: Graceful Termination 

- KEP 2086: Internal Traffic Policy

[Ricardo Katz]

> Does it make sense for you to go try to implement or at least motivate the others?

Well, I did for Calico :) But apparently Cilium got some issue with the way it's built (they are running with this, I'm talking with them).

> I do think we should hold our criteria, but I could see adjusting this to 3 instead of 4 for beta.

If I could change this to 2, I would prefer as I know there are already two :) And maybe some CNI implementations wait for a feature to become beta before implementing it? Otherwise, we can go with 3 without any problem

Thanks!

[Antonio Ojea]

I can take on graceful termination if nobody can, we can add it to the sheet, I think that there is also a PR already

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CAGY4dkmq-VWiOfbOWgr%3DcW5_fnCrOVK4oRKHW-LEwQDJ2Eie8g%40mail.gmail.com.

[Andrew Kim]

Hi folks,

KEPs on my radar for this release:

1. Service InternalTrafficPolicy (https://github.com/kubernetes/enhancements/issues/2086) - @maplain worked on alpha implementation and has volunteered to drive this to Beta, needs e2e tests.

2. Service LoadBalancer Class (https://github.com/kubernetes/enhancements/issues/1959) - @XudongLiuHarold worked on alpha implementation and has volunteered drive this to Beta, needs integration tests.

3. Service Disabling LB Node Ports (https://github.com/kubernetes/enhancements/issues/1864) - @Hanlins has volunteered to promote this to Beta, we added the necessary integration tests during the last release

4. Tracking "Terminating" Condition for EndpointSlice (https://github.com/kubernetes/enhancements/issues/1672) - I'm planning to work on this, milestone TBD, Rob any ideas on when we should promote this to Beta? Integration/e2e tests already added for the condition.

5. kube-proxy gracefully handling terminating endpoints (https://github.com/kubernetes/enhancements/issues/1669) - targeting alpha this release, Antonio I'd love your help with this one if you have the bandwidth.

Thanks,

Andrew Sy

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/CABhP%3DtbT947Jq0wj-qsv0vBOs367e%2Bv16RNQcrf%2Bo%2BHaDLV9dA%40mail.gmail.com.

[Tim Hockin]

I added these 5 to the sheet - please make sure the enhancements issues are up to date WRT links and state.

[bo...@google.com]

Hi all,

I am working on getting https://github.com/kubernetes/enhancements/pull/2728 as well, and will need to get it into the release tracking sheet (https://docs.google.com/spreadsheets/d/1mlui0brYypOAsgS2D13fvcs3At1uMq4i1gWfneq-jxY/edit#gid=0)

[Tim Hockin]

Added it yesterday, though it's technically sig-node I think.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-network/9c0ce236-6ba2-4295-aa94-cb411799b647n%40googlegroups.com.