Tim Usner

It's definitely easier but based on some assumptions/facts: - The `type` of the extension is `shoot-dns-service` - The configuration is of type `Configuration.shoot-dns-service.extensions.config.gardener.cloud` because otherwise we don't know how to...

> Can we use the annotation gardener.cloud/timestamp to identify DNSProviders created by the Gardenlet? As discussed offline, we can use the `managed-dns-provider` role label for the clean-up logic that Gardenlet...

I noticed another thing: The `gardener/gardener-extension-shoot-cert-service` extension or the backing `gardener/cert-management` component uses DNS01 challenges by creating `DNSEntries`. This will result in a direct dependency from `gardener/gardener-extension-shoot-dns-service` to `gardener/gardener-extension-shoot-cert-service` when...

/assign /hold as we wait for Druid v0.11.1, see https://github.com/gardener/gardener/pull/6292#issuecomment-1183003896

Druid v0.11.1 has been merged into Gardener. I plan to continue with this item in the coming days.

Sounds good, thanks @ialidzhikov Some additional thoughts: - `provider.type` must probably become immutable. - > Obviously Shoot provider type (aws, gcp, ...) is different from DNS provider type For convenience...

> But it is not possible to make a newly introduced field (which is optional) required and immutable right away. In the above proposal we could enforce the immutability after...

Thanks for clarifying the points above @ialidzhikov. > The idea can make sense but, if you agree, this rather seems to be out of the scope for this proposal. I...

Have you already thought of adding test cases for the different operating systems that we support on major cloud providers? I know the test matrix easily grows here but at...

> PS. IMO the whole option handling is too hard to follow. +1000