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.

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

Structured Authentication Config #3331

Open
32 of 36 tasks
nabokihms opened this issue Jun 2, 2022 · 36 comments
Open
32 of 36 tasks

Structured Authentication Config #3331

nabokihms opened this issue Jun 2, 2022 · 36 comments
Assignees
@enj @aramase @nabokihms
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/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
SIG Auth Old
Milestone
v1.30

Comments

@nabokihms
Copy link
Member

nabokihms commented Jun 2, 2022 •
edited by enj

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 Jun 2, 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 Jun 2, 2022
@nabokihms nabokihms mentioned this issue Jun 2, 2022
Merged
@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
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 31, 2022
@enj enj added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status lead-opted-in Denotes that an issue has been opted in to a release and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 9, 2022
@enj enj added this to the v1.26 milestone Sep 9, 2022
@rhockenbury rhockenbury added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 20, 2022
@marosset
Copy link
Contributor

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 alpha for 1.26 (correct me, if otherwise)

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

It looks #3332 will address most of these issues.

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 Oct 6, 2022

/milestone v1.27

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.26, v1.27 Oct 6, 2022
@enj enj removed the lead-opted-in Denotes that an issue has been opted in to a release label Oct 6, 2022
@rhockenbury rhockenbury 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 Oct 6, 2022
@nabokihms nabokihms mentioned this issue Oct 10, 2022
Closed
9 tasks
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2023
@enj
Copy link
Member

enj commented Jan 4, 2023

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2023
@enj enj added the lead-opted-in Denotes that an issue has been opted in to a release label Jan 10, 2023
@npolshakova
Copy link

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 alpha for 1.27 (correct me, if otherwise)

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

It looks #3332 will address most of these issues.

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!

@npolshakova
Copy link

npolshakova commented Oct 23, 2023 •
edited

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:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Please make sure to update the issue description with the correct milestone for Alpha release target (x.y) as 1.29 and link the code PRs in the description.

This KEP is currently marked as at risk for code freeze.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

@nabokihms
Copy link
Member Author

@James-Quigley probably it worth writing a blog post even if it is still an alpha feature. I will think about it.

@nabokihms
Copy link
Member Author

@npolshakova I update the title. For now, it seems like all the required code PRs for alpha implementation are merged.

@npolshakova
Copy link

Thanks! Then I can update the status of this KEP as tracked for code freeze. 🚀

@kcmartin
Copy link

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

@aramase aramase mentioned this issue Nov 27, 2023
Merged
@liggitt liggitt modified the milestones: v1.29, v1.30 Jan 3, 2024
@liggitt liggitt added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Jan 3, 2024
@liggitt
Copy link
Member

liggitt commented Jan 3, 2024

Targeting beta in 1.30

@aramase aramase mentioned this issue Jan 22, 2024
Merged
@mickeyboxell
Copy link

mickeyboxell commented Jan 26, 2024 •
edited

Hello @nabokihms 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024:.

This enhancement is targeting for stage beta for v1.30 (correct me, if otherwise)

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: 1.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • KEP readme has up-to-date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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

  • The latest-milestone and stage should be updated to 1.30 and beta in the kep.yaml file.
  • The production readiness review should be completed and updated with the information for the targeting stage beta.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

@aramase aramase mentioned this issue Jan 31, 2024
Merged
@mickeyboxell
Copy link

@aramase please let me know when https://github.com/kubernetes/enhancements/pull/4461/files#diff-e285b55123be991a9360e6cfb15e262247c88492a3eeac345a185818c8caf459 is merged.

@aramase
Copy link
Member

aramase commented Feb 7, 2024

@aramase please let me know when https://github.com/kubernetes/enhancements/pull/4461/files#diff-e285b55123be991a9360e6cfb15e262247c88492a3eeac345a185818c8caf459 is merged.

@mickeyboxell #4461 has been merged! Let me know if anything else is required for the KEP to be marked as tracked.

@aramase aramase mentioned this issue Feb 7, 2024
Merged
@salehsedghpour
Copy link
Contributor

As the PR got merged, this enhancement can now be marked as tracked for enhancement freeze

This was referenced Feb 12, 2024
Merged
Closed
Merged
@mickeyboxell
Copy link

mickeyboxell commented Feb 22, 2024 •
edited

Hey again @aramase 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

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

@mickeyboxell
Copy link

Hi @aramase 👋 Enhancements team here, just a friendly reminder to follow up on the open Enhancement items above prior to code freeze at 02:00 UTC Wednesday 6th March 2024.

@aramase aramase mentioned this issue Mar 5, 2024
Merged
@salehsedghpour
Copy link
Contributor

With the exception request being approved, this can now be marked as tracked for code freeze

This was referenced Mar 24, 2024
Closed
Merged
Merged
This was referenced Apr 9, 2024
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enj enj

@aramase aramase

@nabokihms nabokihms

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/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
(Test board) Kubernetes 1.26 Enhancements Tracking
Status: No status
1.26 Enhancements Tracking
Status: Net New
1.27 Enhancements Tracking
Status: Deferred
1.28 Enhancements Tracking
Status: Removed from Milestone
1.29 Enhancements Tracking
Status: Tracked for Code Freeze
1.30 Enhancements Tracking
Status: Tracked for Doc Freeze
SIG Auth
Status: In Progress
SIG Auth Old
In Review
Milestone
v1.30
Development

No branches or pull requests