API Server Network Proxy

[cheftako]

Enhancement Description

• Move API Server Network Proxy to GA
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1281-network-proxy/README.md
• Primary contact (assignee): @cheftako , @jkh52
• Responsible SIGs: apimachinery, cloud-provider
• Enhancement target (which target equals to which milestone):
  • Beta release target (1.17)
  • GA release target (1.xx)

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[cheftako]

/sig api-machinery

[mrbobbytables]

Hey there @cheftako -- 1.17 Enhancements lead here. It looks like you're targeting to graduate this to beta and already have a PR to add graduation criteria 👍

I'll go ahead and add this to the tracking sheet. As things progress, if you could link to PRs and any tests / testgrid dashboards, that would be greatly appreciated.

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 22 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

Thanks!

/milestone v1.17
/stage beta

[daminisatya]

Hello, @cheftako I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[daminisatya]

Hello @cheftako

Please let us know if this enhancement requires docs. If so, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (4 more days left)

[palnabarun]

Hi @cheftako

I am one of the Enhancements Shadow for the 1.17 Release Team. We are very near to the Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. Can you please link the PR's related to this enhancement here?

Thank you in advance 😄

[daminisatya]

Hello @cheftako

Just a friendly reminder, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (2 more days left)

[mrbobbytables]

👋 @cheftako 1.17 Enhancement lead here -- Just a heads up, an open Docs PR is needed by the end of the day today to remain in the milestone. 😬 If there isn't a PR by EoD, an exception will need to be filed to remain in the 1.17 release.

Please link it here as soon as it's created.

Thanks!

[palnabarun]

Hi @cheftako,

Unfortunately the deadline for filing the docs PR has passed. For now, this enhancement is being removed from the milestone and 1.17 tracking sheet.

If you want to still get this is into this release, please file an enhancement exception.

Thanks!

[palnabarun]

/milestone clear

[kikisdeliveryservice]

Hey there @cheftako -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha|beta|stable in 1.18?
The current release schedule is:
Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released
To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.
If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

[Jefftree]

We are targeting beta for 1.18

[kikisdeliveryservice]

thanks @Jefftree ! 👍

[kikisdeliveryservice]

/milestone v1.18

[iheanyi1]

Hello @cheftako ,

I'm 1.18 docs shadow.

Just want to know if this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time.
Warm regards,

chima

[kikisdeliveryservice]

Hi @cheftako !

As a reminder that the Code Freeze is Thursday 5th March. Can you please link all the k/k PRs or any other PRs that should be tracked for this enhancement?

Thanks!
The 1.18 Enhancements Team

[iheanyi1]

Hello @cheftako ,

I'm 1.18 docs shadow.

Just want to know if this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time.

[caesarxuchao]

No, we don't have new docs in 1.18.

[annajung]

Hi @cheftako, 1.21 Enhancements Lead here.

I'm clearing the milestone to reflect that this enhancement was not entered into the tracking sheet before the enhancements freeze, therefore not opting into the 1.21 release.

/milestone clear

[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-contributor-experience at kubernetes/community.
/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-contributor-experience at kubernetes/community.
/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-contributor-experience at kubernetes/community.
/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-contributor-experience at kubernetes/community.
/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.

[cheftako]

/reopen

[k8s-ci-robot]

@cheftako: Reopened this issue.

In response to this:

/reopen

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.

[cheftako]

/remove-lifecycle rotten

[cheftako]

/assign @jkh52

[jkh52]

Looks like the history is that this was stuck in alpha. (I was under some impression that this was already beta, based on EgressSelectorConfig existing in v1beta* apiserver types.)

We would like to consider beta for 1.28.

Per @deads2k it makes sense to refresh beta criteria against the latest template. I'll update the current beta section and send for review.

[Jefftree]

API Server Network Proxy is in Beta, we probably just forgot to update the tracking information. We reached beta in 1.18 with this PR: kubernetes/kubernetes#88502

I'm sure the KEP template has changed quite a bit since then though.

[jkh52]

@Jefftree thanks for that reference. @deads2k and @cheftako how should we best proceed from a process perspective?

[cheftako]

Time to head for GA then :D

[jkh52]

@cheftako I don't have edit permissions on the title and description, can you refresh it?