Skip to content

KEP-4633: Graduate to Stable. #5279

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 21, 2025
Merged

KEP-4633: Graduate to Stable. #5279

merged 1 commit into from
May 21, 2025
+7 −2

Conversation

vinayakankugoyal
Copy link
Contributor

  • One-line PR description: Graduate KEP-4633 to Stable.
  • Other comments:

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label May 6, 2025
@k8s-ci-robot k8s-ci-robot requested review from enj and johnbelamaric May 6, 2025 20:35
@k8s-ci-robot k8s-ci-robot added kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory sig/auth Categorizes an issue or PR as relevant to SIG Auth. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 6, 2025
@liggitt
Copy link
Member

liggitt commented May 6, 2025

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 6, 2025
@vinayakankugoyal
Copy link
Contributor Author

vinayakankugoyal commented May 7, 2025 •
edited
Loading

@enj - you plan to migrate AuthenticationConfiguration from v1beta1 to v1 for 1.34, right? I am counting on that fact here. Please let me know if anything changes around that.

@enj enj added this to SIG Auth May 7, 2025
@enj enj moved this to Needs Triage in SIG Auth May 7, 2025
@vinayakankugoyal vinayakankugoyal mentioned this pull request May 7, 2025
Open
23 tasks
@aramase aramase moved this from Needs Triage to In Review in SIG Auth May 12, 2025
@enj
Copy link
Member

enj commented May 12, 2025

@enj - you plan to migrate AuthenticationConfiguration from v1beta1 to v1 for 1.34, right? I am counting on that fact here. Please let me know if anything changes around that.

Yeah I plan on GAing the existing functionality + config file but keeping the KEP open and adding new gates to cover the remaining functionality we plan to implement.

@jpbetz
Copy link
Contributor

jpbetz commented May 21, 2025

/approve
For PRR

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpbetz, liggitt, vinayakankugoyal

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 21, 2025
@k8s-ci-robot k8s-ci-robot merged commit 4c66da9 into kubernetes:master May 21, 2025
4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.34 milestone May 21, 2025
@github-project-automation github-project-automation bot moved this from In Review to Closed / Done in SIG Auth May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@enj enj Awaiting requested review from enj

@johnbelamaric johnbelamaric Awaiting requested review from johnbelamaric

Assignees

@liggitt liggitt

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/auth Categorizes an issue or PR as relevant to SIG Auth. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
SIG Auth
Status: Closed / Done
Milestone
v1.34
Development

Successfully merging this pull request may close these issues.
5 participants
@vinayakankugoyal @liggitt @enj @jpbetz @k8s-ci-robot