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

Topology Aware Proxying #2030

Closed
robscott opened this issue Sep 29, 2020 · 13 comments · Fixed by #2666
Closed

Topology Aware Proxying #2030

robscott opened this issue Sep 29, 2020 · 13 comments · Fixed by #2666
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/network Categorizes an issue or PR as relevant to SIG Network. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@robscott
Copy link
Member

robscott commented Sep 29, 2020

Enhancement Description

This is a prerequisite of #2004.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 29, 2020
@robscott
Copy link
Member Author

/sig network

@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 Sep 29, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 30, 2020

Hi @robscott

Pretty sure you know what I'm going to say about Enhancements Freeze (October 6th) and the missing KEP 😆

Will check back in tomorrow.

-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 labels Sep 30, 2020
@robscott
Copy link
Member Author

/assign

@robscott
Copy link
Member Author

Haha sorry for the last minute KEP @kikisdeliveryservice! I've updated this issue to reference the PR. Of course I'd love to get this into 1.20 but realize this is pretty late to get a PR in, so we'll see...

@kikisdeliveryservice
Copy link
Member

The PR LGTM 👍

@kikisdeliveryservice
Copy link
Member

@robscott as a reminder your PR (#2031 ) needs to merge by EOD PST tomorrow October 6th to be included in the 1.20 Release. After that time you will need to request an exception.

@kikisdeliveryservice
Copy link
Member

#2031 merged!! Yay!! 🥳 updating the sheet now.

@kikisdeliveryservice
Copy link
Member

Pretty sure you've seen this before but, official ping 😉

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!
Kirsten

@kcmartin
Copy link

Hello @robscott , 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@kcmartin
Copy link

kcmartin commented Nov 2, 2020

Hi @robscott

The docs placeholder deadline is almost here. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze
Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

@robscott
Copy link
Member Author

robscott commented Nov 5, 2020

Hey @kcmartin and @kikisdeliveryservice, unfortunately I don't think I'll have enough time to get this in for the 1.20 cycle. Will be trying to get it in early in 1.21 instead.

@kikisdeliveryservice kikisdeliveryservice added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Nov 6, 2020
@kikisdeliveryservice kikisdeliveryservice removed this from the v1.20 milestone Nov 6, 2020
@robscott robscott changed the title EndpointSlice Subsetting and Selection Topology Aware Proxying Jan 28, 2021
@robscott
Copy link
Member Author

PR for 1.21 release cycle: #2354

@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-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 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/network Categorizes an issue or PR as relevant to SIG Network. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants