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

Authorize with Field and Label Selectors #4601

Open
8 tasks done
deads2k opened this issue Apr 26, 2024 · 26 comments
Open
8 tasks done

Authorize with Field and Label Selectors #4601

deads2k opened this issue Apr 26, 2024 · 26 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@deads2k
Copy link
Contributor

deads2k commented Apr 26, 2024

Enhancement Description

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

@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 26, 2024
@deads2k
Copy link
Contributor Author

deads2k commented Apr 26, 2024

/sig auth
/milestone 1.31
/stage alpha
/lead opt-in

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 26, 2024
@k8s-ci-robot
Copy link
Contributor

@deads2k: The provided milestone is not valid for this repository. Milestones in this repository: [v1.25, v1.27, v1.28, v1.29, v1.30, v1.31]

Use /milestone clear to clear the milestone.

In response to this:

/sig auth
/milestone 1.31
/stage alpha
/lead opt-in

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/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 26, 2024
@deads2k
Copy link
Contributor Author

deads2k commented Apr 26, 2024

/milestone v1.31

@k8s-ci-robot k8s-ci-robot added this to the v1.31 milestone Apr 26, 2024
@deads2k
Copy link
Contributor Author

deads2k commented Apr 26, 2024

/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Apr 26, 2024
@sreeram-venkitesh
Copy link
Member

sreeram-venkitesh commented Jun 4, 2024

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 alpha for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

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 at risk for enhancement freeze. But I can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

@liggitt
Copy link
Member

liggitt commented Jun 6, 2024

#4600 merged, @deads2k, can you make sure any relevant graduation criteria is mentioned

@MaryamTavakkoli
Copy link

Hello @deads2k 👋, 1.31 Docs Shadow here.
Does this enhancement work planned for 1.31 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, June 27, 2024, 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!

@deads2k
Copy link
Contributor Author

deads2k commented Jun 13, 2024

Graduation criteria added in https://github.com/kubernetes/enhancements/pull/4730/files

@sreeram-venkitesh
Copy link
Member

Thanks @deads2k! Marking this KEP as tracked for enhancements freeze! 🎉

@a-mccarthy
Copy link

Hi @deads2k,

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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.

@sreeram-venkitesh sreeram-venkitesh added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 24, 2024
@Princesso
Copy link

Graduation criteria added in https://github.com/kubernetes/enhancements/pull/4730/files

Hi @deads2k does this mean that this enhancement does not need any new documentation updates?

@liggitt
Copy link
Member

liggitt commented Jun 26, 2024

placeholder doc PR open at kubernetes/website#46986

@a-mccarthy
Copy link

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

@sreeram-venkitesh
Copy link
Member

sreeram-venkitesh commented Jul 7, 2024

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:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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 Tracked for code freeze! Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

@sreeram-venkitesh
Copy link
Member

sreeram-venkitesh commented Jul 17, 2024

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!

@liggitt
Copy link
Member

liggitt commented Jul 19, 2024

The alpha code changes are now merged for 1.31

@sreeram-venkitesh
Copy link
Member

sreeram-venkitesh commented Jul 22, 2024

Thank you! KEP is marked as tracked for code freeze! 🎉

@liggitt liggitt modified the milestones: v1.31, v1.32 Aug 20, 2024
@liggitt liggitt 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 Aug 20, 2024
@liggitt
Copy link
Member

liggitt commented Aug 20, 2024

opting in for beta for 1.32

@impact-maker
Copy link
Member

impact-maker commented Sep 29, 2024

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:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: v1.32.
  • KEP readme has up-to-date graduation criteria.
  • KEP has submitted a production readiness review request for approval and has a reviewer assigned.
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would need to update the following:

  • KEP status is marked as implementable for latest-milestone: v1.32.
  • KEP has submitted a production readiness review request for approval and has a reviewer assigned.
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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!

@liggitt
Copy link
Member

liggitt commented Oct 2, 2024

#4894 should address the outstanding items in #4601 (comment)

@impact-maker
Copy link
Member

@liggitt thanks! Everything looks good, I have updated the issue status to tracked for enhancements freeze

@rashansmith
Copy link

rashansmith commented Oct 14, 2024

Hello @deads2k @liggitt 👋 from the v1.32 Communications Team!
We'd love for you to consider writing a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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.

@AnshumanTripathi
Copy link

Hello @deads2k @liggitt 👋, 1.32 Docs Shadow here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

@liggitt
Copy link
Member

liggitt commented Oct 18, 2024

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo.

opened kubernetes/website#48411

@rashansmith
Copy link

Hello @deads2k @liggitt !

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!

@sftim
Copy link
Contributor

sftim commented Oct 27, 2024

(blog articles are optional)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Tracked for enhancements freeze
Status: In Review
Status: Tracked for Doc Freeze
Development

No branches or pull requests