Ingress dns-controller should be opt-in, not opt-out

[arthur-c]

Hi,

I am starting to happily use external-dns, but I think it should not automatically opt-in for ingresses while using the --ingresses option.

It's an annotation to opt-in for services, but an annotation to opt-out for ingresses.

The annotation for opt-out works well by the way, but it's a strange usage in a declarative configuration world.

Related issues:
#143
#107

[javefang]

Agreed, at least could have an option to set default to be either opt-in or opt-out?

[linki]

@szuecs @ideahitme @mikkeloscar What do you think?

[mikkeloscar]

A flag that would allow either default opt-in or default opt out makes sense to me.

It would be annoying (and a breaking change) to configure every single ingress object for opt-in if you intend to have dns entries out of the box in your cluster/ingress setup.

[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.