-
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
Bound service account token improvements #4193
Comments
Hello @enj 👋, v1.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 Here's where this enhancement currently stands:
For this KEP, everything seems to be done in #4141. Please make sure that the PR is merged in time. The status of this enhancement is marked as |
Hi @enj, 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. It looks like #4141 will address all of the requirements. Please make sure that the changes are merged in time. Let me know if I missed anything. Thanks! |
@sreeram-venkitesh #4141 is now merged. Can you confirm requirements for 1.29 enhancements freeze are met? Thanks! |
@liggitt Thanks for the ping! Yes all the requirements for the enhancements freeze are met. Updating status to |
Hey there @enj @liggitt and @munnerz! 👋, v1.29 Docs Lead here. |
Placeholder PR: kubernetes/website#43590 Please let me know if anything more is needed at this time! Thanks :) |
Hi @enj 👋 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 @enj @munnerz 👋 v1.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:
The status of this KEP is currently As always, we are here to help if any questions come up. Thanks! |
Hello @enj @munnerz 👋, 1.29 Enhancements team here. With all the implementation(code related) PRs merged as per the issue description, this enhancement is now marked as The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. Please let me know if there are additional test PRs we should track. Thanks! |
docs PR reviewed by sig-auth reviewer, ready for docs review at kubernetes/website#43958 |
#4892 should address the outstanding items from #4193 (comment) |
Here’s where this enhancement currently stands:
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. Please keep the issue description up-to-date with appropriate stages as well. Thank you! |
Hello @munnerz, @enj and @liggitt 👋, 1.32 Docs Shadow here. |
Hey there @enj 👋 from the v1.32 Communications Team! We'd love for you to consider writing a feature blog about your enhancement. To opt-in, let us know by opening 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. Note: In your placeholder PR, use |
yup, doc updates incoming cc @munnerz |
Hello @munnerz and @liggitt 👋, Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is 4 days away at Thursday October 24, 2024 18:00 PDT. Thanks, |
Doc update: kubernetes/website#48495 |
Just a reminder, the blog opt-in deadline is close! @munnerz |
Hello @enj @liggitt 👋, Enhancements team here (again 😁 ) With all the implementation(code related) PRs merged as per the issue description: This enhancement is now marked as Please note that KEPs targeting |
Hello 👋, 1.33 Enhancements Lead here. I’m closing milestone 1.32 now. If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the /remove-label lead-opted-in |
/milestone v1.33 We're graduating the last gate to GA for 1.33 |
Hello @enj @liggitt @munnerz 👋, v1.33 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. This enhancement is targeting stage Here’s where this enhancement currently stands:
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 |
Enhancement Description
One-line enhancement description (can be used as a release note): Bound service account token improvements
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/4193-bound-service-account-token-improvements/
Discussion Link: Discussion Link: 2023-08-16 2023-08-02
Primary contact (assignee): @enj
Responsible SIGs: Auth
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s): KEP-4193: bound service account token improvements #4141k/k
) update PR(s): Including JTI & node reference in issued service account tokens (kep 4193) kubernetes#120780k/website
) update PR(s): KEP-4193: bound service account token improvements website#43958Beta
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):Stable
k/enhancements
) update PR(s): KEP-4193: stable updates for 1.32 #4892k/k
) update PR(s): KEP-4193: Promote ServiceAccountTokenJTI, ServiceAccountTokenPodNodeInfo, ServiceAccountTokenNodeBindingValidation to stable kubernetes#128169k/website
) update(s): KEP-4193: Update ServiceAccount admin docs with additional info on bound tokens website#48495Stable ServiceAccountTokenNodeBinding
The text was updated successfully, but these errors were encountered: