Tim Ebert

/priority 4 /remove-lifecycle stale

Thanks @timuthy and @rfranzke for your considerations here. I like your proposals and what you already agreed on :) One question about this step: > * Actual provider migration: Gardenlet...

Small addition: Once, the `DNSProvider` capabilities are moved, we should stop accepting `DNSProvider` in `core.ControllerRegistration.Spec.Resources[].Kind`. There is probably some more code related to references to `DNSProvider` in `ControllerRegistrations` that can...

Before we cleanup `dns.gardener.cloud` related code in this repository, the `DisableDNSProviderManagement` feature gate should be promoted to GA (currently still alpha). Otherwise, it doesn't make sense to have it, because...

Thank you @MartinWeindel. That sounds good 👍

cc @wyb1 @istvanballok

/remove-lifecycle stale

Dedicated go modules in the same repo is painful as experience has shown. As stated in https://github.com/gardener/gardener/issues/2871#issuecomment-949526277, we would need a full sync-out mechanism like kubernetes to better deal with...

I recently got aware of the go workspaces feature as well, which might indeed reduce the pain of having multiple modules in the same repository. But even if that eases...

ref https://github.com/gardener/hvpa-controller/issues/92