-
Notifications
You must be signed in to change notification settings - Fork 526
Make garden access for extensions an explicit opt-in feature #11593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/cherry-pick release-v1.114 |
@rfranzke: once the present PR merges, I will cherry-pick it on top of release-v1.114 in a new PR and assign it to you. In response to this:
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-sigs/prow repository. |
/assign |
6ef8e9f
to
49ab84e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adhering to the principle of least privilege. This is a nice improvement in the security posture of Gardener.
/lgtm
/approve
LGTM label has been added. Git tree hash: 65136bdb109c55ab8875a7c7444671b14e507381
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 2377b53e64dff3eeac0c3b77d8faf4d4713979b8
|
686c490
to
27b09a3
Compare
/cherry-pick release-v1.114 |
@rfranzke: once the present PR merges, I will cherry-pick it on top of release-v1.114 in a new PR and assign it to you. In response to this:
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-sigs/prow repository. |
|
(currently failing since implementation is missing, see following commits)
2bbcee4
to
6e93b51
Compare
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 63f7680aca35961a43d6fa48769688d2bd90e585
|
@rfranzke: new pull request created: #11607 In response to this:
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-sigs/prow repository. |
From gardener#11593, released with `v1.115.0`
From gardener#11593, released with `v1.115.0`
* Cleanup migration logic for e2e upgrade tests From gardener#11593, released with `v1.115.0` * Filter {Managed}Seeds in gardenlet on manager.Manager level gardener#11479, released with `v1.114.0` * No longer generate empy `Secret` for `reconcile` OSC gardener#11004, released with `v1.111.0`
How to categorize this PR?
/area security
/kind enhancement
What this PR does / why we need it:
With #8204, we introduced the automatic injection of a garden cluster kubeconfig into extension deployments in the seed clusters. This PR makes this an explicit opt-in feature (a new field
injectGardenKubeconfig
in theControllerDeployment
must be set totrue
) to make sure only extensions that really request/need it really get this kubeconfig injection ("PoLP").Special notes for your reviewer:
/cc @ScheererJ
FYI @timebertt
Release note: