-
Notifications
You must be signed in to change notification settings - Fork 472
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
Refactor reserve-excess-capacity
Helm chart into Golang component
#6135
Conversation
/lgtm |
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.
Minor suggestion while reviewing the PR with @ialidzhikov
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.
1 inline question.
I was also wondering what is the difference between the reserve-excess-capacity that is deployed as part of the Seed reconciliation and the following extension https://github.com/gardener/reserve-excess-capacity?
/assign @ialidzhikov @ary1992 @shafeeqes @kris94 |
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
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rfranzke 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 |
This is already done by the seedsystem component when removing the relevant object from the ManagedResource secret. Follow-up to gardener#6135
This is already done by the seedsystem component when removing the relevant object from the ManagedResource secret. Follow-up to gardener#6135
…ardenlet (#6186) * Document well-known PriorityClasses * Introduce constants for well-known PriorityClass names Constant names include their purpose as well to make misuse less likely. * Manage well-known Seed PriorityClasses in seedsystem * Deprecated gardener-shoot-controlplane and manage in seedsystem * Manage well-known Shoot PriorityClasses in shootsystem * Drop DeleteReserveExcessCapacity This is already done by the seedsystem component when removing the relevant object from the ManagedResource secret. Follow-up to #6135 * Address suggestions
…ardener#6135) * Add basic template of new `seedsystem` component * Integrate `seedsystem` component into seed reconciliation/deletion flows * Refactor `PriorityClass` template to Golang object * Refactor `Deployment` template to Golang object * Drop no longer required code * Consider `seedsystem` components in seed health check * Address PR review feedback
…ardenlet (gardener#6186) * Document well-known PriorityClasses * Introduce constants for well-known PriorityClass names Constant names include their purpose as well to make misuse less likely. * Manage well-known Seed PriorityClasses in seedsystem * Deprecated gardener-shoot-controlplane and manage in seedsystem * Manage well-known Shoot PriorityClasses in shootsystem * Drop DeleteReserveExcessCapacity This is already done by the seedsystem component when removing the relevant object from the ManagedResource secret. Follow-up to gardener#6135 * Address suggestions
How to categorize this PR?
/area dev-productivity quality robustness
/kind technical-debt test enhancement
/topology seed
/platform all
/exp intermediate
/merge squash
What this PR does / why we need it:
This PR refactors the deployment for the
reserve-excess-capacity
Helm resources. It adopts the component concept. Consequently, it eliminates the Helm resources and adds unit tests, instead. This improves several aspects and the overall code quality.Which issue(s) this PR fixes:
Part of #2754
Release note: