Skip to content
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

Auth API to get self user attributes #3325

Closed
12 tasks done
nabokihms opened this issue May 30, 2022 · 41 comments
Closed
12 tasks done

Auth API to get self user attributes #3325

nabokihms opened this issue May 30, 2022 · 41 comments
Assignees
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@nabokihms
Copy link
Member

nabokihms commented May 30, 2022

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 30, 2022
@nabokihms
Copy link
Member Author

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 30, 2022
@enj enj added this to Needs Triage in SIG Auth Old Jun 6, 2022
@ritazh ritazh moved this from Needs Triage to In Review in SIG Auth Old Jun 6, 2022
@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 22, 2022
@Priyankasaggu11929 Priyankasaggu11929 added this to the v1.25 milestone Jun 22, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 22, 2022

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.
  • KEP status is marked as implementable
  • KEP has a updated detailed test plan section filled out
  • KEP has up to date graduation criteria
  • 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 #3326 for the following points & get it merged by the Enhancements Freeze:

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
Copy link
Member

enj commented Jun 22, 2022

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

@Priyankasaggu11929
Copy link
Member

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
Copy link
Member Author

nabokihms commented Jun 23, 2022

@Priyankasaggu11929 I opened a PR to update the Test Plan section #3423. Thank you for the review!

@Priyankasaggu11929
Copy link
Member

Thanks so much @nabokihms. 🙂

@Priyankasaggu11929
Copy link
Member

With the PR #3423 merged, the enhancement is ready for 1.25 Enhancements Freeze.

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

@Atharva-Shinde
Copy link
Contributor

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

nabokihms added a commit to nabokihms/kubernetes_website that referenced this issue Jul 25, 2022
nabokihms added a commit to nabokihms/kubernetes_website that referenced this issue Jul 29, 2022
nabokihms added a commit to nabokihms/kubernetes_website that referenced this issue Jul 29, 2022
@Atharva-Shinde
Copy link
Contributor

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 kubernetes/kubernetes#111333 merged before the code-freeze :)
The status of the enhancement is still marked as at-risk

@Priyankasaggu11929
Copy link
Member

Hello 👋, 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

@k8s-ci-robot k8s-ci-robot removed this from the v1.25 milestone Aug 3, 2022
@Priyankasaggu11929 Priyankasaggu11929 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Aug 3, 2022
@liggitt liggitt added this to the v1.26 milestone Sep 1, 2022
@liggitt
Copy link
Member

liggitt commented Sep 1, 2022

Retargeted alpha for 1.26

@liggitt liggitt self-assigned this Sep 1, 2022
@liggitt
Copy link
Member

liggitt commented Mar 13, 2023

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

@mickeyboxell
Copy link

mickeyboxell commented Mar 21, 2023

@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!

@nabokihms
Copy link
Member Author

@mickeyboxell PR is opened, yet not merged
kubernetes/website#39794

@liggitt liggitt modified the milestones: v1.27, v1.28 Apr 12, 2023
@liggitt liggitt assigned liggitt and unassigned liggitt and deads2k Apr 19, 2023
@liggitt liggitt added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Apr 26, 2023
@Atharva-Shinde Atharva-Shinde removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release labels May 14, 2023
@enj enj added the lead-opted-in Denotes that an issue has been opted in to a release label May 31, 2023
@Atharva-Shinde
Copy link
Contributor

Hello @nabokihms 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.

Looks like this enhancement is targeting for stage stable for v1.28

Here's where this enhancement currently stands:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone:v1.28
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme 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 simply need to update the following:

  • Add response for this question in the Scalability questionnaire of the KEP readme.
  • Get approval from the PRR authors.

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
Copy link
Member Author

@Atharva-Shinde, I thought this should be enough #3971 (comment) If not, what am I missing?

@Atharva-Shinde
Copy link
Contributor

As this enhancement is targeting stage stable this KEP should have the new question addressed which is not currently as mentioned in my comment above, but as the PRR team seems fine with this I'll mark status of the enhancement as tracked :)

@Atharva-Shinde
Copy link
Contributor

Hey again @nabokihms 👋

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

  • All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
  • All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

This is the code related PR that I found on this KEP issue:

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP.

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

@Atharva-Shinde
Copy link
Contributor

Hey @nabokihms 👋 Enhancements Lead here,
With kubernetes/kubernetes#117713 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!

@enj
Copy link
Member

enj commented Aug 14, 2023

@nabokihms what work is left for this feature?

@nabokihms
Copy link
Member Author

@enj the implementation is finished. What is left:

  • Remove feature gate
  • Mark deprecated and remove alpha and beta APIs

@npolshakova
Copy link

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Aug 27, 2023
@liggitt
Copy link
Member

liggitt commented Aug 28, 2023

This was completed in 1.28 and can be resolved

@enj
Copy link
Member

enj commented Aug 31, 2023

@enj the implementation is finished. What is left:

* Remove feature gate
* Mark deprecated and remove alpha and beta APIs

I have opened kubernetes/kubernetes#120315 to track the post GA work. Closing this issue as complete now that the feature is GA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
Status: Net New
Status: Tracked
Status: Tracked
Archived in project
SIG Auth Old
In Progress
Development

No branches or pull requests