External-dns: Become a full replacement for kops/dns-controller

[linki]

We would like to allow people currently using kops' dns-controller to migrate to ExternalDNS easily. Therefore, ExternalDNS should:

• support all relevant features of dns-controller
• interpret annotations sematically equivalent
• optional: allow both implementations to run side-by-side if that makes for a smoother transition

What's missing in ExternalDNS:

• [x] support for multiple hostnames in ExternalDNS's annotation and its compatibility annotation for kops (https://github.com/kubernetes-incubator/external-dns/issues/197 @jrnt30)
  
  
  
  • @jrnt30 offered to work on it
  
  
• [ ] add a PodSource (https://github.com/kubernetes-incubator/external-dns/issues/195 @sethpollack)
  
  
  
  • watch out for pod IPs, but which DNS name to assign to them?
  
  
  • @sethpollack offered to work on it
  
  
• [x] add a NodeSource (https://github.com/kubernetes-incubator/external-dns/issues/20 @sethpollack)
  
  
  
  • watch out for node IPs, but which DNS name to assign to them?
  
  
  • which node address should be used? private or public? Is that where kops' external/internal annotation comes in?
  
  
  • @sethpollack offered to work on it
  
  
• [ ] support kops' internal/external annotations
  
  
  
  • find out what they do first
  
  

@justinsb added documentation regarding kops in our docs section including semantics about external/internal.

Feel free to comment below and I'll update the description here.

[ideahitme]

multiple annotations issue was addressed in https://github.com/kubernetes-incubator/external-dns/pull/256

[chrislovecnm]

Opened https://github.com/kubernetes/kops/issues/3502 to cross track this. We need to figure out what kops changes we will need as well.

We also have loadbalancer dns records for bastion instance for example as well.

[chrislovecnm]

What is the best way to coloborate on this issue? Here? Office hours?

[jrnt30]

197 is closed. This was addressed in #256

[tamalsaha]

@sethpollack, any update on Pod Source / Node Source?

[sethpollack]

@tamalsaha Its blocked on https://github.com/kubernetes-incubator/external-dns/pull/326

[josdotso]

@sethpollack

Can this proceed now? re: https://github.com/kubernetes-incubator/external-dns/pull/326#issuecomment-367692957

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[LorbusChris]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[Raffo]

Maybe @sethpollack or @justinsb can say something if we want to abandon the plans for this or if it is still something that we want to make happen?

[Raffo]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[LorbusChris]

/remove-lifecycle rotten

[linki]

NodeSource has been added in https://github.com/kubernetes-sigs/external-dns/pull/1218 (included in upcoming v0.5.18)

[linki]

We would like to change the version scheme of ExternalDNS to bump the minor version when larger changes come in.

In the past two years or so we bumped the patch version for all kinds of changes (new providers, new sources, backwards incompatible changes etc.) which is clearly not a good practice.

The reason for this was that we reserved the 0.6 release for kops-compatibility which we didn't achieve yet. Therefore we'd like to assign this issue to a later version in order to free up the next minor version numbers.

/cc @njuettner @Raffo

[njuettner]

Release new version:
https://github.com/kubernetes-sigs/external-dns/releases/tag/v0.6.0

We need to update our milestones ASAP, currently it doesn't align with our roadmap.

[Raffo]

@njuettner we can chat about milestones if you want, just ping me. Otherwise feel free to go on with @linki

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.