search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.43k stars 1.48k forks source link

Structured Authorization Configuration #3221

Open palnabarun opened 2 years ago

palnabarun commented 2 years ago

Enhancement Description

/assign /sig auth

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

tallclair commented 2 years ago

/remove-lifecycle stale

I think we're open to adding this feature, but need someone to drive it forward.

ritazh commented 2 years ago

@palnabarun Are you able to drive this KEP for 1.25?

palnabarun commented 2 years ago

@ritazh -- yes, I am going to drive this in 1.25.

ritazh commented 2 years ago

Hi @palnabarun, any progress on this KEP? Just checking in as enhancements freeze is at 18:00 PST on Thursday June 16, 2022.

Priyankasaggu11929 commented 2 years ago

/milestone v1.25

parul5sahoo commented 2 years ago

Hello @palnabarun 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

Looks like for this one, we would need to update the above mentioned list items before enhancements freeze and update the test plan in the KEP README.md in the PR according to the latest changes in the proposal template incase you wish to add any more information to that section.

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

palnabarun commented 2 years ago

Hi @parul5sahoo, the KEP PR (https://github.com/kubernetes/enhancements/pull/3376) under discussion has been filed with the latest template, has test plans, graduation criteria and a production readiness review is under progress.

Priyankasaggu11929 commented 2 years ago

Just for record & to keep the history intact. (While deleting one of my own), I ended up deleting one of the bot comments by mistake. 😓

Screenshot 2022-06-17 at 10 21 19 AM

The deleted bot comment read following:

@Priyankasaggu11929: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v.125

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.

parul5sahoo commented 2 years ago

Hello @palnabarun :wave:, 1.25 Enhancements team here. The enhancements freeze on 18:00 PST on Thursday June 23, 2022. The enhancements is currently marked as at risk and will be marked as tracked once the PR #3376 is merged. And then it shall be ready for enhancements freeze.

palnabarun commented 2 years ago

We are not targetting it for 1.25 anymore.

ref: https://github.com/kubernetes/enhancements/pull/3376#issuecomment-1164911178

Priyankasaggu11929 commented 2 years ago

Thanks so much for the update @palnabarun. 🙂

/milestone clear

enj commented 2 years ago

/milestone v1.26

rhockenbury commented 2 years ago

Hello @palnabarun 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

rhockenbury commented 2 years ago

Quick reminder - Enhancement freeze is about a week away. If you are still looking to get this enhancement into v1.26, please plan to get #3376 updated and merged.

enj commented 2 years ago

/milestone v1.27

rhockenbury commented 2 years ago

Marking as Removed from Milestone per this comment.

/remove-label tracked/yes /label tracked/no

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

enj commented 1 year ago

/remove-lifecycle stale

marosset commented 1 year ago

Hello @palnabarun 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this enhancement it looks like https://github.com/kubernetes/enhancements/pull/3376 will address most of these requirements.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

liggitt commented 1 year ago

we're picking this back up for 1.28

salehsedghpour commented 1 year ago

Hello @palnabarun 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage alpha for 1.28 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

enj commented 1 year ago

@salehsedghpour #3376 is merged, is this good for v1.28?

palnabarun commented 1 year ago

KEP readme using the latest template has been merged into the k/enhancements repo. KEP has a production readiness review that has been completed and merged into k/enhancements.

@salehsedghpour -- both of the remaining items are done now.

Atharva-Shinde commented 1 year ago

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

VibhorChinda commented 1 year ago

Hello @palnabarun :wave:, 1.28 Docs Shadow here.

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

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

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

Thank you!

salehsedghpour commented 1 year ago

Hey again @palnabarun :wave: Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 . Here’s the enhancement’s state for the upcoming code freeze:

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!

Atharva-Shinde commented 1 year ago

Hello @palnabarun 👋, 1.28 Enhancements Lead here.

Unfortunately, the implementation (code related) PR associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.28 milestone.

If you still wish to progress this enhancement in v1.28, please file an exception request. Thanks!

/milestone clear

ritazh commented 1 year ago

Let's make sure this KEP addresses https://github.com/kubernetes/kubernetes/pull/118571

ritazh commented 1 year ago

/label lead-opted-in

sanchita-07 commented 1 year ago

Hello @palnabarun 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, it looks like merging of #4248 will be good to go for marking the KEP as tracked for enhancement freeze.

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!

ritazh commented 1 year ago

@palnabarun looks like we are missing this. Can you ptal?

KEP readme using the latest template has been merged into the k/enhancements repo.

sanchita-07 commented 1 year ago

Hi @palnabarun, checking in once more as we approach the 1.29 enhancement freeze deadline on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze. It looks like #4248 will address the requirements. Let me know if I missed anything. Thanks!

palnabarun commented 1 year ago

@sanchita-07 -- checking in here, does the KEP not conform to the template or the only blocker is that the pending PR needs to be merged?

liggitt commented 1 year ago

https://github.com/kubernetes/enhancements/pull/4248 is merged, I think we should be all set for 1.29. @sanchita-07, can you confirm?

sanchita-07 commented 1 year ago

Thanks @palnabarun @liggitt :) With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze 🚀. The status of this enhancement is marked as tracked for enhancement freeze. :smiley:

katcosgrove commented 1 year ago

Hey there @liggitt @deads2k @palnabarun and @ritazh :wave:, v1.29 Docs Lead here. Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

palnabarun commented 1 year ago

https://github.com/kubernetes/website/pull/41892 is the docs PR. The feature would require docs.

James-Quigley commented 1 year ago

Hi @palnabarun :wave: from the v1.29 Communications Release Team! We would like to check if you have any plans to publish blogs for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review) Here's the 1.29 Calendar

sanchita-07 commented 1 year ago

Hey again @palnabarun 👋, 1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023:

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs are merged before code freeze:

Are there additional code related PRs that need to be merged for 1.29? It looks like the above mentioned 2 issues are open and its PRs are TBD.

The status for this KEP is currently at risk 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 :)

palnabarun commented 1 year ago

https://github.com/kubernetes/kubernetes/issues/118873 is the only PR remaining to be merged. We will get it merged before the freeze.

palnabarun commented 1 year ago

https://github.com/kubernetes/kubernetes/issues/119102 is optional for Alpha graduation of the feature.

sanchita-07 commented 1 year ago

Hey @palnabarun 👋, 1.29 Enhancements team here!

With all the implementation(code related) PRs merged as per the issue description, and https://github.com/kubernetes/kubernetes/issues/119102 being optional for alpha, this enhancement is now marked as tracked for code freeze for the 1.29 Code Freeze! 🚀

liggitt commented 10 months ago

Targeting beta in 1.30

jpbetz commented 8 months ago

PRR reviewer here, is there a KEP PR to update this enhancement for Beta? Would someone link to it from this issue's description?

enj commented 8 months ago

@jpbetz #4456 is open.

jpbetz commented 8 months ago

I threw a comment on https://github.com/kubernetes/enhancements/pull/4456 but it got missed. Can we get a separate PR to add me as PRR approver for beta in https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-auth/3221.yaml?

liggitt commented 8 months ago

@jpbetz https://github.com/kubernetes/enhancements/pull/4485 open as a follow up

AnaMMedina21 commented 8 months ago

Hello @palnabarun 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage beta forv1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

For this KEP, we would just 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!

liggitt commented 8 months ago

@AnaMMedina21 I think https://github.com/kubernetes/enhancements/pull/4485 is the PR you're looking for to get this KEP in shape for beta (the one you linked is for KEP-3331, not this one). I think I updated to the latest KEP template and answered the new PRR question in that pull request, can you verify that? That PR also adds the beta PRR review record for @jpbetz to complete