Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking Terminating Endpoints #1672

Closed
andrewsykim opened this issue Apr 7, 2020 · 71 comments
Closed

Tracking Terminating Endpoints #1672

andrewsykim opened this issue Apr 7, 2020 · 71 comments
Assignees
@andrewsykim
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
Test-sig-network Obsolete: SIG-Network KEPs (see https...
Milestone
v1.28

Comments

@andrewsykim
Copy link
Member

andrewsykim commented Apr 7, 2020 •
edited by thockin

Enhancement Description

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 7, 2020
@palnabarun
Copy link
Member

Based on the issue description,
/sig network

@k8s-ci-robot
Copy link
Contributor

@palnabarun: The label(s) sig/ cannot be applied, because the repository doesn't have them

In response to this:

Based on the issue description,
/sig network

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.

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 17, 2020
@harshanarayana
Copy link

Hey there @andrewsykim -- 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:

  1. The KEP PR must be merged in an implementable state
  2. The KEP must have test plans
  3. 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!

@harshanarayana
Copy link

Hey @andrewsykim, 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. 🖖

@harshanarayana
Copy link

Hey @andrewsykim , Enhancements team shadow here for the release v1.19 cycle.

I am just following up to see if this enhancement item is still being planned for v1.19 so that we can start tracking the details in the tracker sheet. Please let me know if it is planned to inclusion and I will update the trackers accordingly.

Thanks

@harshanarayana harshanarayana added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 20, 2020
@harshanarayana
Copy link

Hey @andrewsykim , Unfortunately the deadline for the 1.19 Enhancement freeze has passed and there is no KEP PR opened/merged in implemetable state yet.. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 18, 2020
@palnabarun
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2020
@thockin thockin added this to Proposed in Test-sig-network Sep 4, 2020
@thockin thockin moved this from Proposed to To Do in Test-sig-network Sep 4, 2020
@thockin thockin moved this from To Do to Proposed in Test-sig-network Sep 4, 2020
@kikisdeliveryservice
Copy link
Member

@andrewsykim

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

@kikisdeliveryservice
Copy link
Member

Hi @andrewsykim

Enhancements Freeze is October 6th. Currently there is not KEP associated with this Issue. Please advise on whether you intend on working on this for 1.20.

As a reminder to be included in a release:

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

Thanks,
Kirsten

Closed
@andrewsykim
Copy link
Member Author

Sorry @kikisdeliveryservice this KEP was merged in v1.19, forgot to update the description with a link

@kikisdeliveryservice
Copy link
Member

Hi @andrewsykim

Thanks could you clarify the graduation criteria? It links to another KEP whose graduation criteria talks about beta and doesn't seem to mention this ?

As a reminder Enhancements Freeze is next week October 6th , so please update the KEP to have clear graduation criteria by then.

Thanks!
Kirsten
/milestone v1.20

@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Sep 30, 2020
@kikisdeliveryservice kikisdeliveryservice added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Sep 30, 2020
@andrewsykim
Copy link
Member Author

Updated alpha graduation criteria here #2065

@kikisdeliveryservice
Copy link
Member

@andrewsykim perfect! thank you!

@kikisdeliveryservice
Copy link
Member

This merged, updated sheet!

@kendallroden
Copy link

Hey @andrewsykim!

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thanks so much,

Kendall

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Nov 9, 2022
@andrewsykim andrewsykim mentioned this issue Nov 9, 2022
Merged
3 tasks
@andrewsykim
Copy link
Member Author

Oops, sorry I forgot to link -- but the PR landed here kubernetes/kubernetes#113363

@krol3
Copy link

krol3 commented Nov 14, 2022

Hello @andrewsykim 👋please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before deadline Tuesday 15th November 2022. Thank you!

@andrewsykim andrewsykim mentioned this issue Nov 15, 2022
Closed
@andrewsykim
Copy link
Member Author

docs: kubernetes/website#37913

@leonardpahlke
Copy link
Member

@rhockenbury It looks like all the requirements are met and we can add it back to the milestone
cc @kubernetes/release-team-leads

@leonardpahlke
Copy link
Member

It looks like we removed this from the K8s 1.26 release cycle because we didn't find the PR that @andrewsykim linked above. The PR was merged a week before the code freeze, so this needs to be added back into the tracking.

/milestone v1.26
/label tracked/yes
/label lead-opted-in
/remove-label tracked/no

FYI release-docs @krol3, release-comms @fsmunoz for tracking

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Nov 28, 2022
@k8s-ci-robot k8s-ci-robot added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Nov 28, 2022
@marosset
Copy link
Contributor

Hi @andrewsykim - since this enhancement has graduated to stable can you please update https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/1672-tracking-terminating-endpoints/kep.yaml setting the status to implemented and then close this issue.

Thanks!

@marosset marosset removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels Dec 14, 2022
@thockin thockin modified the milestones: v1.26, v1.28 Jan 5, 2023
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2023
@thockin thockin removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2023
@thockin
Copy link
Member

thockin commented Apr 5, 2023

@andrewsykim can you update the main issue here with release numbers?

@robscott robscott mentioned this issue Apr 13, 2023
Merged
5 tasks
@thockin
Copy link
Member

thockin commented Apr 27, 2023

NEXT: Remove gate in 1.28

@thockin thockin mentioned this issue Apr 27, 2023
Merged
@thockin thockin moved this from GA (merged, gate not removed) to DONE (GA, merged, gate removed) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Apr 28, 2023
@thockin
Copy link
Member

thockin commented Apr 28, 2023

DONE

@thockin thockin closed this as completed Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewsykim andrewsykim

Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
(Test board) Kubernetes 1.26 Enhancements Tracking
Status: New New
1.26 Enhancements Tracking
Status: Graduating
Obsolete: SIG-Network KEPs (see https...
DONE (GA, merged, gate removed)
Test-sig-network
  
To Do
Milestone
v1.28
Development

No branches or pull requests