Structured Authorization Configuration

[palnabarun]

Enhancement Description

• One-line enhancement description: Adds ability to structure configuring authorizers and add multiple webhooks to the kube-apiserver authorization chain
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3221-structured-authorization-configuration
• Discussion Link: Add a provision to add multiple authorization webhooks kubernetes#101762
• Primary contact (assignee): @palnabarun @ritazh
• Responsible SIGs: sig-auth
• Enhancement target (which target equals to which milestone):
  • Alpha release target: 1.29
  • Beta release target: 1.30
  • Stable release target (x.y): 1.32
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3221: Add Structured Authorization Configuration KEP #3376
    • KEP-3221: Update for 1.29 #4161
    • 3221: update KEP according to 1.29 requirements #4248
  • Code (k/k) update PR(s):
    • Issue: [StructuredAuthorizationConfig] - Implement AuthorizationConfiguration kubernetes#118872
      • [StructuredAuthorizationConfiguration] Implement API types and wire kube-apiserver to use them kubernetes#119099
      • [StructuredAuthorizationConfiguration] Add --authorization-config flag and guard it using a Feature Gate kubernetes#120154
    • Issue: [StructuredAuthorizationConfig] - CEL integration kubernetes#118873,
      • [StructuredAuthorizationConfig] - CEL integration kubernetes#121223
  • Docs (k/website) update PR(s)
    • Add docs for Authorization Configuration website#41892
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3221 - WIP 1.30 update #4456
    • KEP-3221: Add PRR, update metrics #4485
  • Code (k/k) update PR(s):
    • KEP-3221: Implement authorization configuration file reloading kubernetes#121946
    • Add allowed/denied metrics for authorizers kubernetes#123333
    • Add authz webhook matchcondition metrics kubernetes#123611
    • Add authorization webhook duration/count/failopen metrics kubernetes#123639
    • Duplicate v1alpha1 AuthorizationConfiguration to v1beta1 kubernetes#123640
    • Promote StructuredAuthorizationConfiguration feature gate to beta kubernetes#123641
  • Docs (k/website) update(s): Add docs for Structured Authz beta website#45138
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-3221: update kep milestone and stage #4796
  • Code (k/k) update PR(s): KEP-3221: Promote StructuredAuthorizationConfiguration to GA kubernetes#128172
  • Docs (k/website) update(s): KEP-3221: Promote StructuredAuthorizationConfiguration to GA website#48424

/assign
/sig auth

[k8s-triage-robot]

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

[tallclair]

/remove-lifecycle stale

I think we're open to adding this feature, but need someone to drive it forward.

[ritazh]

@palnabarun Are you able to drive this KEP for 1.25?

[palnabarun]

@ritazh -- yes, I am going to drive this in 1.25.

[ritazh]

Hi @palnabarun, any progress on this KEP? Just checking in as enhancements freeze is at 18:00 PST on Thursday June 16, 2022.

[Priyankasaggu11929]

/milestone v1.25

[parul5sahoo]

Hello @palnabarun 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

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 need to update the above mentioned list items before enhancements freeze and update the test plan in the KEP README.md in the PR according to the latest changes in the proposal template incase you wish to add any more information to that section.

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!

[palnabarun]

Hi @parul5sahoo, the KEP PR (#3376) under discussion has been filed with the latest template, has test plans, graduation criteria and a production readiness review is under progress.

[Priyankasaggu11929]

Just for record & to keep the history intact. (While deleting one of my own), I ended up deleting one of the bot comments by mistake. 😓

The deleted bot comment read following:

@Priyankasaggu11929: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v.125

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[parul5sahoo]

Hello @palnabarun 👋, 1.25 Enhancements team here.
The enhancements freeze on 18:00 PST on Thursday June 23, 2022. The enhancements is currently marked as at risk and will be marked as tracked once the PR #3376 is merged. And then it shall be ready for enhancements freeze.

[palnabarun]

We are not targetting it for 1.25 anymore.

ref: #3376 (comment)

[Priyankasaggu11929]

Thanks so much for the update @palnabarun. 🙂

/milestone clear

[enj]

/milestone v1.26

[liggitt]

All implementation PRs are now merged for beta / 1.30

[sreeram-venkitesh]

Hi @palnabarun 👋, 1.31 Enhancements Lead here.

If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze.

/remove-label lead-opted-in

[liggitt]

opting in for stable graduation in 1.32

[shecodesmagic]

Hello @palnabarun @ritazh 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage stable for v.132 (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: { CURRENT_RELEASE }. 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 submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

[michellengnx]

Hello @palnabarun, @ritazh, @liggitt and @deads2k 👋, 1.32 Docs Shadow here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[sftim]

(this will need a docs update PR; pretty much all beta to stable graduations should have one)

[rytswd]

Hi @palnabarun @ritazh 👋 -- this is Ryota (@rytswd) from the v1.32 Communications Team!

For the v1.32 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 30th Oct 2024? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[liggitt]

Docs PR open at kubernetes/website#48424

[rytswd]

Hi @palnabarun @ritazh @liggitt 👋, v1.32 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 30th Oct. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[shecodesmagic]

Hello @ritazh @palnabarun 👋, Enhancements team here (again 😁 )

With all the implementation(code related) PRs merged as per the issue description:

• KEP-3221: Promote StructuredAuthorizationConfiguration to GA kubernetes#128172

This enhancement is now marked as tracked for code freeze for the v1.32 Code Freeze!

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged and the feature gates are removed.