External-DNS crash loop due to nil error in DNSEntry object

[koorikla]

Bug Report

What happened:

When defining app-%!s(<nil>)-internal-eks.eu-west-1.sandbox as a DNS entry, the External-DNS pod successfully creates the entries in Route53 and then enters a crash loop due to a nil error.

The entrys were manually removed from route53 console to recover external-dns pod.

apiVersion: dns.gardener.cloud/v1alpha1 kind: DNSEntry metadata: name: app-%!s(<nil>)-internal-eks spec: dnsName: "app-%!s(<nil>)-internal-eks.eu-west-1.sandbox"

What you expected to happen:
external-dns pod to log a error instead of crashing

The External-DNS pod should create the DNS entry without crashing.

How to reproduce it (as minimally and precisely as possible):

1. Define app-%!s(<nil>)-internal-eks.eu-west-1.com as a DNS entry in the DNSEntry objects.
2. Observe the External-DNS pod successfully creating the entries in Route53.
3. Check the pod logs to confirm the crash loop due to the nil error.

• External-DNS version: v20240321-v0.14.1
• DNS provider: Route53