Add feature gate metadata for structured authz config

Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>
This commit is contained in:
Anish Ramasekar 2024-03-19 14:02:50 -07:00
parent 3b6274d696
commit c4e3177ff3
No known key found for this signature in database
GPG Key ID: E96F745A34A409C2
2 changed files with 6 additions and 2 deletions

View File

@ -211,7 +211,7 @@ so an earlier module has higher priority to allow or deny a request.
## Configuring the API Server using an Authorization Config File
{{< feature-state state="beta" for_k8s_version="v1.30" >}}
{{< feature-state feature_gate_name="StructuredAuthorizationConfiguration" >}}
The Kubernetes API server's authorizer chain can be configured using a
configuration file.
@ -220,7 +220,7 @@ This feature enables the creation of authorization chains with multiple webhooks
You must specify the path to the authorization configuration using the `--authorization-config`command line argument. If you want to keep using command line flags instead of a configuration file, those will continue to work as-is. To gain access to new authorization webhook capabilities like multiple webhooks, failure policy, and pre-filter rules, switch to putting options in an `--authorization-config` file.
Starting Kubernetes 1.30, the configuration file format is
Starting Kubernetes v{{< skew currentVersion >}}, the configuration file format is
beta-level, and only requires specifying `--authorization-config` since the `StructuredAuthorizationConfiguration` feature gate is enabled by default.
{{< caution >}}

View File

@ -9,6 +9,10 @@ stages:
- stage: alpha
defaultValue: false
fromVersion: "1.29"
toVersion: "1.29"
- stage: beta
defaultValue: true
fromVersion: "1.30"
---
Enable structured authorization configuration, so that cluster administrators
can specify more than one [authorization webhook](/docs/reference/access-authn-authz/webhook/)