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

Namespace Scoped Ingress Class Parameters #2365

Closed
4 tasks done
robscott opened this issue Jan 29, 2021 · 32 comments
Closed
4 tasks done

Namespace Scoped Ingress Class Parameters #2365

robscott opened this issue Jan 29, 2021 · 32 comments
Assignees
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
Milestone

Comments

@robscott
Copy link
Member

robscott commented Jan 29, 2021

Enhancement Description

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

/sig network
/cc @danehans

@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 Jan 29, 2021
@robscott
Copy link
Member Author

/assign

@annajung annajung 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 Feb 9, 2021
@annajung annajung added this to the v1.21 milestone Feb 9, 2021
@hbagdi
Copy link
Contributor

hbagdi commented Feb 18, 2021

/assign

@kendallroden
Copy link

Hi @robscott ,
Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

  • Tuesday, March 9th: Week 9 - Code Freeze
  • Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
    • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them. Currently have one tracked:

Thanks!

@robscott
Copy link
Member Author

Hey @kendallnelson, thanks for the reminder on this! @hbagdi is leading the development of this enhancement and I think we're still on track to get things in before these deadlines. We'll let you know if anything changes.

@hbagdi
Copy link
Contributor

hbagdi commented Feb 26, 2021

@kendallnelson I've opened up a placeholder PR for docs: kubernetes/website#26723. Thanks for the reminders!

@kendallroden
Copy link

Not sure if you meant to @ me but thanks for these updates :) @hbagdi

@kendallroden
Copy link

@hbagdi Hey there! Just a quick reminder that Code freeze is 5 days away, March 9th EOD PST
Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back. Looks like your placeholder PR for docs is all good :D
Thanks!

@hbagdi
Copy link
Contributor

hbagdi commented Mar 7, 2021

@kendallnelson An update: code PR for this enhancement has been merged and the docs PR is open (kubernetes/website#26723).

@JamesLaverack JamesLaverack 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 Apr 25, 2021
@JamesLaverack
Copy link
Member

/milestone v1.22
/stage beta

@k8s-ci-robot k8s-ci-robot added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels May 1, 2021
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.21, v1.22 May 1, 2021
@JamesLaverack JamesLaverack added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels May 1, 2021
@reylejano
Copy link
Member

Hi @hbagdi ,

With kubernetes/kubernetes#101711, you're all set for the 1.22 code freeze which starts on July 8, 2021 🎉

With kubernetes/website#28693, you're set for the 1.22 Docs Placeholder PR deadline on July 9, 2021 🎉

@salaxander salaxander 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 Aug 19, 2021
@salaxander
Copy link

/milestone v1.23

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.22, v1.23 Sep 3, 2021
@salaxander salaxander added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Sep 3, 2021
@salaxander
Copy link

Hi @hbagdi! 1.23 Enhancements team here. Just checking in as we approach enhancements freeze at 11:59pm PST on Thursday 09/09. Here's where this enhancement currently stands:

  • Updated KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a test plan section filled out.
  • KEP has up to date graduation criteria.
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like we're all set for enhancements freeze!

Thanks!

@nate-double-u
Copy link

Hi @hbagdi 👋 1.23 Docs shadow here.

This enhancement is marked as Needs Docs for the 1.23 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.23 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu November 18, 11:59 PM PDT.

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

Thanks!

@salaxander
Copy link

Hi @hbagdi - Since today is code freeze, I just want to confirm that all k/k PRs for this KEP have merged?

@hbagdi
Copy link
Contributor

hbagdi commented Nov 16, 2021

I think so.

@thockin thockin moved this from Beta gated (merged) to GA (merged, gate not removed) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Jan 6, 2022
@gracenng
Copy link
Member

gracenng commented Jan 9, 2022

Marked as impletemented for stable

@gracenng gracenng closed this as completed Jan 9, 2022
@gracenng gracenng removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 9, 2022
@gracenng gracenng removed this from the v1.23 milestone Jan 9, 2022
@hbagdi
Copy link
Contributor

hbagdi commented Jan 11, 2022

@robscott We need to remove the gate in 1.24, is that correct?

@thockin thockin added this to the v1.22 milestone Jan 20, 2022
@thockin thockin modified the milestones: v1.22, v1.25 Feb 16, 2022
@thockin
Copy link
Member

thockin commented Feb 16, 2022

Reminder: Remove gate in 1.25, milestone updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Obsolete: SIG-Network KEPs (see https...
DONE (GA, merged, gate removed)
Development

No branches or pull requests