flush all record external-dns created

[ensonic]

When undeploying a cluster for google cloud-dns the zone should be emptied. Right now one would need to remove the services and wait 'a bit' until external-dns removed the dns-record, then undeploy external-dns.
It would be nice to have a way to either force updating the records or having a way to flush the added records manually.

[hjacobs]

I guess creating a script to iterate through all DNS records "owned" by External DNS (e.g. identified by TXT record) should be easy to do. I don't see this as part of the External DNS "core".

[ensonic]

I've considered this. Unfortunately gcloud dns does not make this easy. Deleting a record requires you to specify all fields. One can filter like this:

gcloud dns record-sets list --zone=external-dns --format=json | jq '. | map(select(.type == "A" or .type == "TXT"))'

but generating the transaction from this list is still not trivial :/

[ideahitme]

Thanks for the idea.

IMO there might be a certain use for this feature, though I don't see it coming in the nearest future, as for now we are more concentrated on core components - dns providers, compatibility and refactoring, having a functionality to flush the records will probably not come before we will stabilise the "where's" and "how's" the records are managed on dns provider side and how they are generated from k8s resources.

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