I am using 0.5.18 tag of external-dns (registry.opensource.zalan.do/teapot/external-dns:0.5.18) with AWS route53 and created new record with kube's ingress resources using following:
annotations:
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/certificate-arn: ${route53_certificate}
alb.ingress.kubernetes.io/ssl-policy: ELBSecurityPolicy-2016-08
external-dns.alpha.kubernetes.io/hostname: ${somedns_com}
if I go ahead and update this ingress resource for dns entry or delete the ingress resource, it doesn't delete the record from Record53. I thought they entry should be deleted by default if ingress resource gets deleted.
Please check the container policy argument on your external-dns pod to be set to sync. I think the default value is upsert-only, which will prevent external-dns from deleting any DNS records.
Yep, it was set to upsert-only, I will update it to sync. Thanks for the response.
Most helpful comment
Please check the container
policyargument on your external-dns pod to be set tosync. I think the default value isupsert-only, which will prevent external-dns from deleting any DNS records.