cheftako commented 4 years ago

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 commented 4 years ago

/sig api-machinery

mrbobbytables commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 :smile:

daminisatya commented 4 years ago

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 commented 4 years ago

👋 @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 commented 4 years ago

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 commented 4 years ago

/milestone clear

kikisdeliveryservice commented 4 years ago

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 commented 4 years ago

We are targeting beta for 1.18

kikisdeliveryservice commented 4 years ago

thanks @Jefftree ! 👍

kikisdeliveryservice commented 4 years ago

/milestone v1.18

iheanyi1 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

iheanyi1 commented 4 years ago

Thanks for clarifications

iheanyi1 commented 4 years ago

Thank you @caesarxuchao for update

jeremyrickard commented 4 years ago

Hello @cheftako @caesarxuchao

We're getting close to code freeze on 05 March 2020. Please list or link to all PRs that are in flight for this enhancement.

Jefftree commented 4 years ago

They're tracked in this issue: https://github.com/kubernetes/kubernetes/issues/85250

VineethReddy02 commented 4 years ago

Hi @cheftako We have already completed docs deadline i.e March 16th docs should be in ready to merge state. I see @caesarxuchao raised a docs placeholder PR pointing this enhancement. Can I know the status of the docs asap?

harshanarayana commented 4 years ago

Hey there @cheftako, 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

The KEP PR must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria.

The current release schedule is:

Monday, April 13: Week 1 - Release cycle begins
Tuesday, May 19: Week 6 - Enhancements Freeze
Thursday, June 25: Week 11 - Code Freeze
Thursday, July 9: Week 14 - Docs must be completed and reviewed
Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

palnabarun commented 4 years ago

/milestone clear

(since the Enhancement graduated to Beta in Kubernetes 1.18)

harshanarayana commented 4 years ago

Hey @cheftako, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

Jefftree commented 4 years ago

Hi @harshanarayana. This graduated to beta in 1.18 and we don't have any major changes to be included in 1.19.

harshanarayana commented 4 years ago

Hey @Jefftree, thanks for following up on this with an update. I have update the tracking sheet accordingly. 🖖

Thanks

fejta-bot commented 3 years ago

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

palnabarun commented 3 years ago

/remove-lifecycle stale

spiffxp commented 3 years ago

I would be interested to know what needs to be done to allow us to gain enough confidence to remove the old ssh tunneling functionality (https://github.com/kubernetes/kubernetes/pull/75330); @cheftako mentions there that it'd be preferable see this move to GA beforehand, but I'm not sure what is involved in that

kikisdeliveryservice commented 3 years ago

Hi @Jefftree @cheftako

Enhancements Lead here. Any plans for this in 1.20?

Thanks! Kirsten

kikisdeliveryservice commented 3 years ago

Hi @Jefftree @cheftako

Enhancements Lead here. Any plans for this in 1.20? If you intend to graduate to stable, you need to update the graduation criteria by Enhancements Freeze next week Tuesday October 6th

Thanks! Kirsten

fejta-bot commented 3 years ago

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

mindw commented 3 years ago

/remove-lifecycle stale

frittentheke commented 3 years ago

@cheftako The link to the KEP is currently broken ... likely due to https://github.com/kubernetes/enhancements/commit/b9b8b52c1e8830a9c7d7065315d9675bf93f0d04 by @wojtek-t

annajung commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

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 commented 2 years ago

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 commented 2 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/1281#issuecomment-877556935): >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](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

cheftako commented 1 year ago

/reopen

k8s-ci-robot commented 1 year ago

@cheftako: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/1281#issuecomment-1521196031): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

cheftako commented 1 year ago

/remove-lifecycle rotten

cheftako commented 1 year ago

/assign @jkh52

jkh52 commented 1 year ago

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 commented 1 year ago

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: https://github.com/kubernetes/kubernetes/pull/88502

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

jkh52 commented 1 year ago

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

cheftako commented 1 year ago

Time to head for GA then :D

jkh52 commented 1 year ago

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

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

kubernetes / enhancements

API Server Network Proxy #1281

Enhancement Description