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
Structured Authorization Configuration #3221
Comments
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 |
/remove-lifecycle stale I think we're open to adding this feature, but need someone to drive it forward. |
@palnabarun Are you able to drive this KEP for 1.25? |
@ritazh -- yes, I am going to drive this in 1.25. |
Hi @palnabarun, any progress on this KEP? Just checking in as enhancements freeze is at 18:00 PST on Thursday June 16, 2022. |
/milestone v1.25 |
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 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 |
Hi @parul5sahoo, the KEP PR (#3376) under discussion has been filed with the latest template, has test plans, graduation criteria and a production readiness review is under progress. |
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. 😓 The deleted bot comment read following:
|
Hello @palnabarun 👋, 1.25 Enhancements team here. |
We are not targetting it for 1.25 anymore. ref: #3376 (comment) |
Thanks so much for the update @palnabarun. 🙂 /milestone clear |
/milestone v1.26 |
kubernetes/website#41892 is the docs PR. The feature would require docs. |
Hi @palnabarun 👋 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. |
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 Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
kubernetes/kubernetes#118873 is the only PR remaining to be merged. We will get it merged before the freeze. |
kubernetes/kubernetes#119102 is optional for Alpha graduation of the feature. |
Hey @palnabarun 👋, 1.29 Enhancements team here! With all the implementation(code related) PRs merged as per the issue description, |
Targeting beta in 1.30 |
PRR reviewer here, is there a KEP PR to update this enhancement for Beta? Would someone link to it from this issue's description? |
I threw a comment on #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? |
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 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 |
@AnaMMedina21 I think #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 |
@liggitt ah, yes, thanks for that correction! sorry about that. |
#4485 is merged, I think we're set for enhancements freeze |
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 Here's where this enhancement currently stands:
The status of this enhancement is marked as |
Hi @palnabarun 👋, 1.30 Docs Shadow here. Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hey again @palnabarun 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. These are the two I have:
|
All implementation PRs are now merged for beta / 1.30 |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s)k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s): Add docs for Structured Authz beta website#45138/assign
/sig auth
The text was updated successfully, but these errors were encountered: