-
Notifications
You must be signed in to change notification settings - Fork 450
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
Introduce core.gardener.cloud/v1.ControllerDeployment
API
#9771
Introduce core.gardener.cloud/v1.ControllerDeployment
API
#9771
Conversation
/retest |
/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.
Love it :) Looking forward. Thank you very much!
Thanks, done. PTAL :) |
API reference docs cannot be generated for empty API groups, so the generation will be added later once the first resource has been added.
This is a prerequisite for implementing conversion from the `v1beta1` API to the new structure in the internal and `v1` API version.
…ControllerDeployment`
…ntrollerDeployment`
46171a0
to
1319a4b
Compare
Done :) |
I think we are good to go. Let's get this in, especially since it's a prerequisite for other features (cc @maboehm @kon-angelo @vknabel). Thanks for your efforts 🎉 /lgtm |
LGTM label has been added. Git tree hash: 0bf337020733a38ed7a143214c40a5da1af866b8
|
[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 |
/retest |
(from gardener#9771, released with `v1.96.0`)
(from gardener#9771, released with `v1.96.0`)
How to categorize this PR?
/area dev-productivity usability
/kind enhancement
What this PR does / why we need it:
This PR introduces the new
core.gardener.cloud/v1
API version including theControllerDeployment
resource.The v1 API drops support for custom types and replaces
providerConfig
with a proper API structure for helm-basedControllerDeployments
.gardener-apiserver stores the
ControllerDeployment
resource in the v1 version but can perform lossless conversion from and tov1beta1
.The new API version is introduced to support further developments augmenting helm-based
ControllerDeployments
(e.g., OCI registry support instead of raw charts).As we move away from the
providerConfig
approach, we need a new API version.All other
core.gardener.cloud
resources are still only available inv1beta1
. This PR lays the foundation for graduating other resources tov1
later on as well.Which issue(s) this PR fixes:
Part of #9773
Special notes for your reviewer:
Co-Authored-By: @maboehm
Release note:
A new `core.gardener.cloud/v1` API version is introduced which only includes the `ControllerDeployment` resource for now. The new version of the `ControllerDeployment` drops the `type` and `providerConfig` fields in favor of a well-structured section for helm-based `ControllerDeployments`.