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

Open
3 of 4 tasks
nabokihms opened this issue May 30, 2022 · 19 comments
Open
3 of 4 tasks

Auth API to get self user attributes #3325

nabokihms opened this issue May 30, 2022 · 19 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
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

nabokihms commented May 30, 2022

/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 Jun 6, 2022
@ritazh ritazh moved this from Needs Triage to In Review in SIG Auth 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

Priyankasaggu11929 commented Jun 23, 2022

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

Priyankasaggu11929 commented Jun 23, 2022

Thanks so much @nabokihms. 🙂

@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 23, 2022

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

Atharva-Shinde commented Jul 25, 2022

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

Atharva-Shinde commented Aug 1, 2022

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

Priyankasaggu11929 commented Aug 3, 2022

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 liggitt added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status 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 and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Sep 6, 2022
@liggitt
Copy link
Member

liggitt commented Sep 6, 2022

@deads2k deads2k self-assigned this Sep 14, 2022
@Atharva-Shinde
Copy link

Atharva-Shinde commented Sep 20, 2022

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.
  • KEP status is marked as implementable
  • KEP has an 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.

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

nabokihms commented Sep 24, 2022

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

nabokihms added a commit to nabokihms/kubernetes_website that referenced this issue Oct 3, 2022
@enj enj moved this from In Review to In Progress in SIG Auth Oct 3, 2022
@Atharva-Shinde
Copy link

Atharva-Shinde commented Oct 4, 2022

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

rhockenbury commented Oct 29, 2022

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:

  • 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.

Let me know if you need to track any PRs beyond kubernetes/kubernetes#111333.

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

@nabokihms
Copy link
Member Author

nabokihms commented Oct 29, 2022

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

krol3 commented Nov 9, 2022

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

liggitt commented Nov 9, 2022

kubernetes/website#35385 is open (and linked from the description) and has lgtm

k8s-ci-robot pushed a commit to kubernetes/website that referenced this issue Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Net New
SIG Auth
In Progress
Development

No branches or pull requests

9 participants