[Request] Add Support for Hetzner DNS

[danielr1996]

What would you like to be added:
Hello, I'd like to have a provider for the Hetzner DNS Service. Is there any option for out of tree provider that I can maintain myself, or do they have to be included in tree? If they are out of tree I'd be happy to write my own implementation.

Why is this needed:

Hetzner is a big hosting company from Germany with very competetive pricing and currently beta support in kops
Their DNS Service is free, offers a well documented API and allows to set almost every DNS record unlike some other providers.

References
API Doc
go library for Hetzner DNS I've written a few years ago, though not sure if it's up to date

[kladiv]

+1

[jonasbadstuebner]

See #3192

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Raffo]

As stated in other issues, this project is not going to add additional providers and will use the webhook provider to integrate new ones. https://github.com/mconfalonieri/external-dns-hetzner-webhook is a current provider supporting hetzner that can be used to interact with hetzner. Closing this issue, feel free to reopen if there are further questions.