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 Authentication Config #3331
Comments
/sig auth |
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 |
Hello @nabokihms 👋, 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 Here's where this enhancement currently stands:
It looks #3332 will address most of these issues. The status of this enhancement is marked as |
/milestone v1.27 |
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 |
Hello @nabokihms 👋, 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 Here's where this enhancement currently stands:
It looks #3332 will address most of these issues. The status of this enhancement is marked as |
Hello @nabokihms 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023. 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 |
lgtm @enj |
Hi @nabokihms 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! |
Hey @nabokihms , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
I've opened kubernetes/website#41999 for the docs. FYI @nabokihms. |
Hey @nabokihms Enhancements team here 👋 Just checking in as we approach Code freeze at 01:00 UTC Here’s the enhancement’s state for the upcoming code freeze:
I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above. As always, we are here to help if any questions come up. Thanks! |
Hello @nabokihms 👋, 1.28 Enhancements Lead here. Unfortunately, the implementation (code related) PRs 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 |
Hello @nabokihms 👋, 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 Here's where this enhancement currently stands:
The status of this enhancement is marked as |
@jeremyrickard This is going to be alpha in 1.29 |
Hey there @aramase @enj and @nabokihms! 👋, v1.29 Docs Lead here. |
I've opened a placeholder PR for the doc update: kubernetes/website#43397 |
Hi @nabokihms 👋 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 @nabokihms 👋 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:
Please make sure to update the issue description with the correct milestone for This KEP is currently marked as Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
@James-Quigley probably it worth writing a blog post even if it is still an alpha feature. I will think about it. |
@npolshakova I update the title. For now, it seems like all the required code PRs for alpha implementation are merged. |
Thanks! Then I can update the status of this KEP as |
@nabokihms Hi, 1.29 Comms Team again! You indicated you were thinking about writing a blog post for this feature. A reminder that today (November 14, 2023) is the deadline for opening a Draft blog PR. Would you please update us about your plans? |
Enhancement Description
k/enhancements
) update PR(s): KEP-3331: Structured Authentication Config #3332k/k
) update PR(s):--authentication-config
flag kubernetes#119142k/website
) update PR(s): add docs for StructuredAuthenticationConfig v1alpha1 website#43397Please 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: