Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions content/en/docs/reference/access-authn-authz/node.md
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nit)
Can we move

In future releases, the node authorizer may add or remove permissions to ensure
kubelets have the minimal set of permissions required to operate correctly.

earlier in this page?

Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,7 @@ Read operations:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Restrictions based on associated Node

{{< feature-state feature_gate_name="AuthorizeNodeWithSelectors" >}}

When the `AuthorizeNodeWithSelectors` feature is enabled
(along with the pre-requisite `AuthorizeWithSelectors` feature),
kubelets are only allowed to read their own Node objects,
and are only allowed to read pods bound to their node.
Kubelets are limited to reading their own Node objects, and only reading pods bound to their node.

Write operations:

Expand Down
5 changes: 3 additions & 2 deletions content/en/docs/reference/access-authn-authz/webhook.md
Original file line number Diff line number Diff line change
Expand Up @@ -166,8 +166,9 @@ Access to non-resource paths are sent as:

{{< feature-state feature_gate_name="AuthorizeWithSelectors" >}}

With the `AuthorizeWithSelectors` feature enabled, field and label selectors in the request
are passed to the authorization webhook. The webhook can make authorization decisions
When calling out to an authorization webhook, Kubernetes passes
label and field selectors in the request to the authorization webhook.
The authorization webhook can make authorization decisions
informed by the scoped field and label selectors, if it wishes.

The [SubjectAccessReview API documentation](/docs/reference/kubernetes-api/authorization-resources/subject-access-review-v1/)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,9 @@ stages:
- stage: beta
defaultValue: true
fromVersion: "1.32"
toVersion: "1.33"
- stage: stable
defaultValue: true
fromVersion: "1.34"
---
Make the [Node authorizer](/docs/reference/access-authn-authz/node/) use fine-grained selector authorization.
Requires `AuthorizeWithSelectors` to be enabled.
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ stages:
- stage: beta
defaultValue: true
fromVersion: "1.32"
toVersion: "1.33"
- stage: stable
defaultValue: true
fromVersion: "1.34"
---
Allows authorization to use field and label selectors.
Enables `fieldSelector` and `labelSelector` fields in the [SubjectAccessReview API](/docs/reference/kubernetes-api/authorization-resources/subject-access-review-v1/),
Expand Down
5 changes: 3 additions & 2 deletions content/en/docs/reference/using-api/cel.md
Original file line number Diff line number Diff line change
Expand Up @@ -413,9 +413,10 @@ To perform an authorization check for a service account:
</tbody>
</table>

{{< feature-state state="alpha" for_k8s_version="v1.31" >}}
{{< feature-state feature_gate_name="AuthorizeWithSelectors" >}}

With the alpha `AuthorizeWithSelectors` feature enabled, field and label selectors can be added to authorization checks.
For CEL expressions in the API where a variable of type `Authorizer` is available,
field and label selectors can be included in authorization checks.

<table>
<caption>Examples of CEL expressions using selector authorization functions</caption>
Expand Down