Auth API to get self user attributes

[nabokihms]

Enhancement Description

• One-line enhancement description (can be used as a release note): Auth API to get self user attributes

• Kubernetes Enhancement Proposal:

• Discussion Link:

  • Internal sig-auth Slack discussion https://kubernetes.slack.com/archives/C0EN96KUY/p1647544566605239
  • Sig-AUTH Bi-Weekly Meeting for 20220511 https://youtu.be/E4NJcGYTUis?t=120

• Primary contact (assignee): @nabokihms

• Responsible SIGs: sig-auth

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): v1.26
  • Beta release target (x.y): v1.27
  • Stable release target (x.y): v1.28

• [x] Alpha

  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3326
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/111333
  • [x] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/35385

• [ ] Beta

  • [ ] KEP (k/enhancements) update PR(s):
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[nabokihms]

/sig auth

[Priyankasaggu11929]

Hello @nabokihms 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PT on Thursday June 23, 2022, which is just over 2 days from now.

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

Here's where this enhancement currently stands:

• [ ] KEP file using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable
• [ ] KEP has a updated detailed test plan section filled out
• [x] KEP has up to date graduation criteria
• [x] KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would require updating the open KEP PR https://github.com/kubernetes/enhancements/pull/3326 for the following points & get it merged by the Enhancements Freeze:

• update the kep.yaml file to add status: implementable.
• update the Test Plan section as per the updated details listed here
• add a approved PRR for stage alpha

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!

[enj]

@Priyankasaggu11929 I believe this is good for v1.25?

[Priyankasaggu11929]

Hello @enj @nabokihms, the PR addressed all the checklist items but missed updating the Test Plan section as per the updated details listed here.

Could you please update that as well. Thank you so much! 🙂

[nabokihms]

@Priyankasaggu11929 I opened a PR to update the Test Plan section https://github.com/kubernetes/enhancements/pull/3423. Thank you for the review!

[Priyankasaggu11929]

Thanks so much @nabokihms. 🙂

[Priyankasaggu11929]

With the PR https://github.com/kubernetes/enhancements/pull/3423 merged, the enhancement is ready for 1.25 Enhancements Freeze.

For note, the status is now marked as tracked. Thank you!

[Atharva-Shinde]

Hi @nabokihms, Enhancements team here again 👋

Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure that the following items are completed before the code-freeze:

• [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PRs are fully merged by the code freeze deadline.

Currently, the status of the enhancement is marked as at-risk

Thanks :)

[Atharva-Shinde]

Hey @nabokihms reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022. Try to get this PR https://github.com/kubernetes/kubernetes/pull/111333 merged before the code-freeze :) The status of the enhancement is still marked as at-risk

[Priyankasaggu11929]

Hello :wave:, 1.25 Enhancements Lead here.

Unfortunately, this enhancement did not meet the code freeze criteria because there are still unmerged k/k code PRs.

If you still wish to progress this enhancement in v1.25, please file an exception request. Thank you so much!

/milestone clear

[liggitt]

Retargeted alpha for 1.26

[liggitt]

Applying labels for 1.26 per https://groups.google.com/a/kubernetes.io/g/dev/c/R1afPL7zpT4/m/lKv7eg3jBwAJ

[Atharva-Shinde]

Hey @nabokihms @liggitt @deads2k 👋, 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:

• [ ] KEP file using the latest template has been merged into the k/enhancements repo.
• [X] KEP status is marked as implementable
• [ ] KEP has an updated detailed test plan section filled out
• [X] KEP has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would need to:

• The KEP needs updating it's Test Plan Section to incorporate details as stated in the updated detailed test plan
  • We need to include the acknowledgement which is missing in this enhancements Test Plan
• Update the kep.yaml to reflect the current milestone information
• Include the new updated PR of this KEP in the Issue Description and get it merged before Enhancements Freeze to make this enhancement eligible for 1.26 release.

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 :)

[nabokihms]

@Atharva-Shinde I opened the PR to fix KEP composition problems. Could you please check whether it covers what you've asked for?

[Atharva-Shinde]

Hey @nabokihms @liggitt @deads2k as the PR #3543 is merged with all the required changes, I've updated the status of this KEP to tracked for v1.26 release cycle :)

[rhockenbury]

Hi @nabokihms 👋,

Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

• [X] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [X] All PRs are fully merged by the code freeze deadline.

Let me know if you need to track any PRs beyond https://github.com/kubernetes/kubernetes/pull/111333.

As always, we are here to help should questions come up. Thanks!

[nabokihms]

@rhockenbury Thank you for checking. According to the code, everything is merged and ready for the Alpha. We are only waiting for the documentation.

[krol3]

Hello @nabokihms 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Any doubt, reach us! Thank you!

[liggitt]

https://github.com/kubernetes/website/pull/35385 is open (and linked from the description) and has lgtm

[marosset]

/remove-label lead-opted-in /remove-label tracked/yes /label tracked/no /milestone clear

[liggitt]

@nabokihms are you available to help progress this to beta in 1.27?

[nabokihms]

Yes, I will prepare PRs for this.

[liggitt]

Yes, I will prepare Pars for this.

excellent... I'd suggest starting with an update to the KEP doc / yaml file in this repo, updating dates for 1.27 and double-checking any graduation criteria. you can tag me on the PR for that

[marosset]

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 beta for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.27
• [x] KEP readme has a updated detailed test plan section filled out
• [x] KEP readme has up to date graduation criteria
• [x] KEP has a production readiness review that has been completed and merged into k/enhancements.

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

• Please update the latest-milestone in the kep.yaml

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!

[nabokihms]

@marosset sorry for the delay, PR is opened https://github.com/kubernetes/enhancements/pull/3823

[marosset]

Great!

I'm marking this enhancement as tracked for v1.27.

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

[katmutua]

Hello @nabokihms 👋🏾 !

@katmutua 1.27 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

If you already have existing open PRs please link them to the description so we can easily track them. Thanks!

[shatoboar]

Hi @nabokihms 👋, Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:

• [X] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [X] All PRs are fully merged by the code freeze deadline.
  • https://github.com/kubernetes/kubernetes/pull/116274

Please let me know what other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks!

[liggitt]

all k/k PRs are merged, this is complete for code freeze

[mickeyboxell]

@liggitt @nabokihms @deads2k was there a Docs PR opened against dev-1.27 branch in the k/website repo?

If not, please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review as soon as possible. 01:00 UTC Wednesday 22nd March 2023 / 17:00 PDT Tuesday 21st March 2023 is the official deadline.

This PR will need a doc review by Tuesday 4th April 2023 to get this into the release. Please reach out to required SIGs to get their review. Thank you!