Allow replica count to be set to zero

[josh-ferrell]

Description
Allows the replica count for external-dns deployments to be configurable as zero. external-dns helm installs can be done in secondary regions with zero replicas waiting to be scaled up during a failover event. See #4783

The helm chart values.yaml was commented to reflect that external-dns does not support more than one replica.

Checklist

• Unit tests updated
• End user documentation updated

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign stevehipwell for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• charts/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ivankatliarchuk]

You may need to add some validation as well. Not sure if external DNS supports HA mode werry well. Having 2+ replicas may throttle DNS API as at the moment there is no leader election.

[ivankatliarchuk]

The problem is described here a bit #2430. Had a DNS outage once due to this behaviour.

[k8s-ci-robot]

PR needs rebase.

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-sigs/prow repository.

[mloiseleur]

@josh-ferrell Would you please add some validation ? It should fail with replica > 1.

FTM, external-dns does not work with more than one pod.