DNS Records fail to create against an nginx-ingress provisioned against a DigitalOcean Loadbalancer + hostname annotation applied

[finxtech]

What happened:

DNS Records fail to create against an nginx ingress provisioned against a DigitalOcean Loadbalancer with the hostname annotation applied.

annotation: 
   service.beta.kubernetes.io/do-loadbalancer-hostname:

The annotation is applied on the nginx-ingress which results in the LoadBalancer ExternalIP showing as the hostname and not External IP address.

Its seems like a chicken and egg scenario in that even if i apply the external-dns.alpha.kubernetes.io/hostname annotation against the loadbalancer service, external-dns fails because it then tries to create a CNAME DNS record against A record that doesnt yet exist for the load balancer external IP.

Perhaps i'm missing a flag or some documentation somewhere but the only way i get this to continue to work against new ingresses/service deployed after is manually creating an A record against a cloud provisioned LB with an unknown IP which breaks the whole automation process.

What you expected to happen:

Im not sure if its designed to do this but i was expecting an A record to be created against the ingress hostname using the LB external IP address when the ingress service is created.

Anything else we need to know?:

Environment:

• External-DNS version: v0.12.2
• DNS provider: Cloudflare
• Others: DigitalOcean LoadBalancer

[finxtech]

The controller is configured also to listen for service/ingress events. I also tried adding the external dns hostname annotation on the ingress service itself which fails because it attempts to create a CNAME record against an A record which doesnt exist.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.