-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Authorize with Field and Label Selectors #4601
Comments
/sig auth |
@deads2k: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
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. |
/milestone v1.31 |
/label lead-opted-in |
Hello @deads2k 👋, v1.31 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we need to do the following:
Rest everything looks good to me, everything seems to be taken care of in #4600. Please get the KEP files merged before the enhancements freeze and update the issue description with the links to the KEP and the PR. The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you! |
Hello @deads2k 👋, 1.31 Docs Shadow here. |
Graduation criteria added in https://github.com/kubernetes/enhancements/pull/4730/files |
Thanks @deads2k! Marking this KEP as |
Hi @deads2k, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release. |
Hi @deads2k does this mean that this enhancement does not need any new documentation updates? |
placeholder doc PR open at kubernetes/website#46986 |
@deads2k, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
Hey again @deads2k 👋 v1.31 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP): If you anticipate missing code freeze, you can file an exception request in advance. Marking this KEP as |
Hi again @deads2k @liggitt! We're a week away from code freeze and I wanted to ping you here as a small reminder for getting kubernetes/kubernetes#125571 merged in time. Please let me know if there are any other PRs that we should be tracking for this KEP! Thanks! |
The alpha code changes are now merged for 1.31 |
Thank you! KEP is marked as |
opting in for beta for 1.32 |
Hello @liggitt 👋, v1.32 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024. This enhancement is targeting for stage beta for v1.32 (correct me, if otherwise). Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you! If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
#4894 should address the outstanding items in #4601 (comment) |
@liggitt thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze |
Hello @deads2k @liggitt 👋 from the v1.32 Communications Team! To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. |
Hello @deads2k @liggitt 👋, 1.32 Docs Shadow here. |
opened kubernetes/website#48411 |
This is a reminder to author your feature blog post! To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. Please feel free to reach out if you have any questions! |
(blog articles are optional) |
Enhancement Description
One-line enhancement description (can be used as a release note): allow using field and label selectors in authorization decisions
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/4601-authorize-with-selectors
Discussion Link:
Primary contact (assignee): @deads2k
Responsible SIGs: sig-auth
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s): KEP-4601: Beta updates for 1.32 #4894k/k
) update PR(s): KEP-4601: AuthorizeNodeWithSelectors / AuthorizeWithSelectors to beta kubernetes#128168k/website
) update(s): KEP-4601: Promote AuthorizeWithSelectors / AuthorizeNodeWithSelectors to beta website#48411Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: