Tracking Terminating Endpoints

[andrewsykim]

Enhancement Description

• One-line enhancement description (can be used as a release note): Track terminating endpoints so we can handle terminating endpoints gracefully.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1672-tracking-terminating-endpoints
• Primary contact (assignee): @andrewsykim
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target: v1.20
  • Beta release: v1.22
  • Stable release target: v1.28

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

[palnabarun]

Based on the issue description,
/sig network

[k8s-ci-robot]

@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.

[harshanarayana]

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]

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]

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]

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]

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]

/remove-lifecycle stale

[kikisdeliveryservice]

@andrewsykim

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[kikisdeliveryservice]

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

[andrewsykim]

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

[kikisdeliveryservice]

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

[andrewsykim]

Updated alpha graduation criteria here #2065

[kikisdeliveryservice]

@andrewsykim perfect! thank you!

[kikisdeliveryservice]

This merged, updated sheet!

[kendallroden]

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

[andrewsykim]

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

[krol3]

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]

docs: kubernetes/website#37913

[leonardpahlke]

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

[leonardpahlke]

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

[marosset]

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!

[k8s-triage-robot]

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

[thockin]

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

[thockin]

NEXT: Remove gate in 1.28

[thockin]

DONE