-
Notifications
You must be signed in to change notification settings - Fork 527
Renew all garden access secrets on seed when triggered by annotation #8152
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
Renew all garden access secrets on seed when triggered by annotation #8152
Conversation
With this, we can renew the garden access secrets in all namespaces in the next commit without renewing shoot access secrets. In the future, the shoot/garden controller should also restrict the call to the `shoot` class. However, the controller in `gardener-resource-manager` is still not configured with the class, hence it is still responsible for all secrets. This is fine for now since resource-manager and the call to `RenewAccessSecrets` are restricted to the `garden` or shoot namespace, but in the future we should make sure that we restrict it to the `shoot` class to prevent potential future responsibility overlaps.
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.
awesome PR, thanks 🚀
/assign |
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.
Awesome PR :)
@rfranzke @oliver-goetz thanks for your reviews, PTAL :) |
/lgtm |
LGTM label has been added. Git tree hash: 5c5b42f9bcc52f98383efe260642654d3b58482b
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oliver-goetz 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 |
@timebertt: The following test failed, say
Full PR test history. Your PR dashboard. Command help for this repository. 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. I understand the commands that are listed here. |
…ardener#8152) * Nit: move the `tokenrequestor` controller docs out of the `shoot` controller section * Add documentation for the new feature * Validate operation annotation on `Seeds` * Bump `Seed` generation when the operation annotation is set * Allow selecting class in `RenewAccessSecrets` With this, we can renew the garden access secrets in all namespaces in the next commit without renewing shoot access secrets. In the future, the shoot/garden controller should also restrict the call to the `shoot` class. However, the controller in `gardener-resource-manager` is still not configured with the class, hence it is still responsible for all secrets. This is fine for now since resource-manager and the call to `RenewAccessSecrets` are restricted to the `garden` or shoot namespace, but in the future we should make sure that we restrict it to the `shoot` class to prevent potential future responsibility overlaps. * Renew all garden access secrets on seed when triggered by annotation * Verify garden access token renewal in e2e tests * Address review suggestions
…ardener#8152) * Nit: move the `tokenrequestor` controller docs out of the `shoot` controller section * Add documentation for the new feature * Validate operation annotation on `Seeds` * Bump `Seed` generation when the operation annotation is set * Allow selecting class in `RenewAccessSecrets` With this, we can renew the garden access secrets in all namespaces in the next commit without renewing shoot access secrets. In the future, the shoot/garden controller should also restrict the call to the `shoot` class. However, the controller in `gardener-resource-manager` is still not configured with the class, hence it is still responsible for all secrets. This is fine for now since resource-manager and the call to `RenewAccessSecrets` are restricted to the `garden` or shoot namespace, but in the future we should make sure that we restrict it to the `shoot` class to prevent potential future responsibility overlaps. * Renew all garden access secrets on seed when triggered by annotation * Verify garden access token renewal in e2e tests * Address review suggestions
follow-up of gardener#8152, released with `v1.74.0`
* Remove MCM legacy CRD deletion follow-up of #8559, released with `v1.82.0` * Remove legacy `shoot-node-logging` MR cleanup follow-up of #8501, released with `v1.80.0` * Remove MCM legacy resources cleanup in generic `Worker` actuator follow-up of #8596, released with `v1.82.0` * Restrict GRM's token requestor to secrets with `class=shoot` follow-up of #8152, released with `v1.74.0` * Remove support for deprecated `NetworkPolicy` annotations follow-up of #7907, released with `v1.71.0`
How to categorize this PR?
/area security usability
/kind enhancement
What this PR does / why we need it:
This PR adds a mechanism for renewing all garden access secrets on a given seed by annotating it with
gardener.cloud/operation=renew-garden-access-secrets
.ref #8032 (comment)
Which issue(s) this PR fixes:
Part of #8001
Special notes for your reviewer:
/cc @oliver-goetz @rfranzke
Release note: