Remove 'experimental' disclaimer for Seed{Authorizer,Restriction} features
#4326
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gardener-robot
added
area/documentation
krgostev
pushed a commit
to krgostev/gardener
that referenced
this pull request
Apr 21, 2022
krgostev
pushed a commit
to krgostev/gardener
that referenced
this pull request
Jul 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How to categorize this PR?
/area security documentation
/kind enhancement
What this PR does / why we need it:
This PR removes the 'experimental' disclaimer for the
Seed{Authorizer,Restriction}features. It is considered ready and can be used for production landscapes.Which issue(s) this PR fixes:
Fixes #1723
Release note:
Similar to the [`NodeAuthorizer`](https://kubernetes.io/docs/reference/access-authn-authz/node/) and [`NodeRestriction`](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#noderestriction) features in Kubernetes (preventing kubelets from accessing resources which aren't associated with their responsible `Node`s), Gardener does now have a `SeedAuthorizer` and `SeedRestriction` feature (preventing gardenlets from accessing resources which aren't associated with their `Seed`s). If you want to enable it for your landscapes then please consult [this document](https://github.com/gardener/gardener/blob/master/docs/deployment/gardenlet_api_access.md).