enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Structured Authentication Config

Open nabokihms opened this issue 3 years ago • 79 comments

Enhancement Description

  • One-line enhancement description (can be used as a release note): Structured Authentication Config

  • Kubernetes Enhancement Proposal: KEP

  • Discussion Link:

    • Slack post - https://kubernetes.slack.com/archives/C0EN96KUY/p1638208007167400
    • Google doc - https://docs.google.com/document/d/1sY8fRyRtk4eG9R439z5ao5i9bFuuxilS03XaNlqoni0/edit?disco=AAAARL1K8OE

  • Primary contact (assignee): @aramase @enj @nabokihms

  • Responsible SIGs: sig-auth

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

    • Alpha release target (x.y): v1.29
    • Beta release target (x.y): v1.30
    • Stable release target (x.y): v1.34

  • [x] Alpha

    • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3332
    • [x] Code (k/k) update PR(s):
      • [x] https://github.com/kubernetes/kubernetes/pull/118984
      • [x] https://github.com/kubernetes/kubernetes/pull/119142
      • [x] https://github.com/kubernetes/kubernetes/pull/120183
      • [x] https://github.com/kubernetes/kubernetes/pull/121078
      • [x] https://github.com/kubernetes/kubernetes/pull/121709
    • [x] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/43397

  • [x] Beta

    • [x] KEP (k/enhancements) update PR(s):
      • [x] https://github.com/kubernetes/enhancements/pull/4461
      • [x] https://github.com/kubernetes/enhancements/pull/4491
      • [x] https://github.com/kubernetes/enhancements/pull/4844
    • [x] Code (k/k) update PR(s):
      • [x] https://github.com/kubernetes/kubernetes/pull/121622
      • [x] https://github.com/kubernetes/kubernetes/pull/122560
      • [x] https://github.com/kubernetes/kubernetes/pull/122975
      • [x] https://github.com/kubernetes/kubernetes/pull/123165
      • [x] https://github.com/kubernetes/kubernetes/pull/123225
      • [x] https://github.com/kubernetes/kubernetes/pull/123282
      • [x] https://github.com/kubernetes/kubernetes/pull/123305
      • [x] https://github.com/kubernetes/kubernetes/pull/123431
      • [x] https://github.com/kubernetes/kubernetes/pull/123458
      • [x] https://github.com/kubernetes/kubernetes/pull/123525
      • [x] https://github.com/kubernetes/kubernetes/pull/123527
      • [x] https://github.com/kubernetes/kubernetes/pull/123561
      • [x] https://github.com/kubernetes/kubernetes/pull/123568
      • [x] https://github.com/kubernetes/kubernetes/pull/123696
      • [x] https://github.com/kubernetes/kubernetes/pull/123719
      • [x] https://github.com/kubernetes/kubernetes/pull/123721
      • [x] https://github.com/kubernetes/kubernetes/pull/123737
      • [x] https://github.com/kubernetes/kubernetes/pull/123793
      • [x] https://github.com/kubernetes/kubernetes/pull/123856
      • [x] https://github.com/kubernetes/kubernetes/pull/127010
      • [x] https://github.com/kubernetes/kubernetes/pull/126553
    • [x] Docs (k/website) update(s):
      • [x] https://github.com/kubernetes/website/pull/45106
      • [x] https://github.com/kubernetes/website/pull/45108
      • [x] https://github.com/kubernetes/website/pull/47821

  • [ ] Stable - 1.34

    • [x] KEP (k/enhancements) update PR(s):
      • [x] https://github.com/kubernetes/enhancements/pull/5305
      • [x] https://github.com/kubernetes/enhancements/pull/5332
    • [ ] Code (k/k) update PR(s):
      • [ ] https://github.com/kubernetes/kubernetes/pull/123642
      • [x] https://github.com/kubernetes/kubernetes/pull/131536
      • [x] https://github.com/kubernetes/kubernetes/pull/131573
      • [x] https://github.com/kubernetes/kubernetes/pull/131574
      • [x] https://github.com/kubernetes/kubernetes/pull/131752
      • [x] https://github.com/kubernetes/kubernetes/pull/131798
      • [x] https://github.com/kubernetes/kubernetes/pull/131916
      • [x] https://github.com/kubernetes/kubernetes/pull/132082
    • [x] Docs (k/website) update(s):
      • [x] https://github.com/kubernetes/website/pull/51290

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

nabokihms avatar Jun 02 '22 14:06 nabokihms

/sig auth

nabokihms avatar Jun 02 '22 14:06 nabokihms

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-triage-robot avatar Aug 31 '22 14:08 k8s-triage-robot

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 https://github.com/kubernetes/enhancements/pull/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!

marosset avatar Sep 20 '22 23:09 marosset

/milestone v1.27

enj avatar Oct 06 '22 15:10 enj

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-triage-robot avatar Jan 04 '23 21:01 k8s-triage-robot

/remove-lifecycle stale

enj avatar Jan 04 '23 22:01 enj

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 avatar Jan 31 '23 15:01 npolshakova

/assign @enj @aramase

We will work on nailing the API down in 1.27 but target 1.28 for implementation.

enj avatar Feb 09 '23 15:02 enj

/milestone v1.28

enj avatar Mar 21 '23 15:03 enj

Hello @nabokihms 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023.

This enhancement is targeting for stage alpha for v1.28 (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.
  • [x] KEP status is marked as implementable for latest-milestone: v1.28
  • [ ] KEP readme has a updated detailed test plan section filled out
  • [x] 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 just need to update the following:

  • Fill out the test plan section
  • Edit Kep status from provisional to implementable
  • Create the production readiness review file and complete it.
  • Ensure that the PRs are merged

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!

Kasambx avatar Jun 03 '23 15:06 Kasambx

@Kasambx #3332 is merged, let me know if this needs anything else for v1.28.

enj avatar Jun 13 '23 18:06 enj

lgtm @enj

Kasambx avatar Jun 15 '23 07:06 Kasambx

Hi @nabokihms

1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

AdminTurnedDevOps avatar Jun 21 '23 17:06 AdminTurnedDevOps

Hey @nabokihms , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

Rishit-dagli avatar Jul 12 '23 15:07 Rishit-dagli

Hey @nabokihms , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

I've opened https://github.com/kubernetes/website/pull/41999 for the docs. FYI @nabokihms.

aramase avatar Jul 12 '23 16:07 aramase

Hey @nabokihms Enhancements team here :wave:

Just checking in as we approach Code freeze at 01:00 UTC ~~Friday~~ Wednesday, 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.

I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above.

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

Atharva-Shinde avatar Jul 18 '23 16:07 Atharva-Shinde

Hello @nabokihms 👋, 1.28 Enhancements Lead here.

Unfortunately, the implementation (code related) PRs associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.28 milestone.

  • https://github.com/kubernetes/kubernetes/pull/119142
  • https://github.com/kubernetes/kubernetes/pull/118984

If you still wish to progress this enhancement in v1.28, please file an exception request. Thanks!

/milestone clear

Atharva-Shinde avatar Jul 19 '23 02:07 Atharva-Shinde

Hello @nabokihms 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (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.
  • [x] KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
  • [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 more information on the PRR process, check here). As this enhancement just changed its milestone to 1.29 there isn't a need for a new PRR unless there are major changes to the KEP questionnaire.

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

npolshakova avatar Sep 22 '23 16:09 npolshakova

@enj @aramase is this graduating to beta in 1.29 or staying in alpha?

jeremyrickard avatar Oct 02 '23 00:10 jeremyrickard

@enj @aramase is this graduating to beta in 1.29 or staying in alpha?

@jeremyrickard This is going to be alpha in 1.29

aramase avatar Oct 02 '23 00:10 aramase

Hey there @aramase @enj and @nabokihms! :wave:, v1.29 Docs Lead here. Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

katcosgrove avatar Oct 09 '23 08:10 katcosgrove

Hey there @aramase @enj and @nabokihms! 👋, v1.29 Docs Lead here. Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

I've opened a placeholder PR for the doc update: https://github.com/kubernetes/website/pull/43397

aramase avatar Oct 10 '23 00:10 aramase

Hi @nabokihms :wave: from the v1.29 Communications Release Team! We would like to check if you have any plans to publish blogs for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review) Here's the 1.29 Calendar

James-Quigley avatar Oct 23 '23 14:10 James-Quigley

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:

  • [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 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!

npolshakova avatar Oct 23 '23 18:10 npolshakova

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

nabokihms avatar Oct 23 '23 18:10 nabokihms

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

nabokihms avatar Oct 23 '23 21:10 nabokihms

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

npolshakova avatar Oct 24 '23 14:10 npolshakova

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

kcmartin avatar Nov 14 '23 20:11 kcmartin

Targeting beta in 1.30

liggitt avatar Jan 03 '24 14:01 liggitt

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:

  • [X] KEP readme using the latest template has been merged into the k/enhancements repo.
  • [x] 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.
  • [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 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!

mickeyboxell avatar Jan 26 '24 16:01 mickeyboxell