Doesn't create TXT records version 2 (GCP) and recreated dns records for root domain

[zakabluk]

What happened:
I updated from version 0.13.4 to 0.14.0 thought version 0.13.5 with launched once with flag '--once', as asked in release note for 0.13.6 link.
Than I faced with same errors for all my zones in Google Cloud DNS which delegatet from CF and has manual records
NS - ns-cloud-d1.googledomains.com. ....
SOA - ns-cloud-d1.googledomains.com. ....

time="2023-11-15T12:53:00Z" level=info msg="Change zone: cropper batch #0"
time="2023-11-15T12:53:00Z" level=info msg="Del records: domain.dom. A [1.1.1.1] 300"
time="2023-11-15T12:53:00Z" level=info msg="Del records: domain.dom. TXT [\"heritage=external-dns,external-dns/owner=owner,external-dns/resource=ingress/cropper-prod/cropper-prod\"] 300"
time="2023-11-15T12:53:00Z" level=info msg="Add records: domain.dom. A [1.1.1.1] 300"
time="2023-11-15T12:53:00Z" level=info msg="Add records: domain.dom. TXT [\"heritage=external-dns,external-dns/owner=owner,external-dns/resource=ingress/cropper-prod/cropper-prod\"] 300"

and than repeate all time delete/create records.

I noticed that External DNS created only one TXT record which didn't have prefix 'a-'. For not root domain records external-dns generate two records. As mentioned in #3167 I tried to added falg --txt-wildcard-replacement , but secondary records didn't turn out. And recreate records process continie as well.

What you expected to happen:
DNS records created only once without delete process.

Environment:

• External-DNS version (use external-dns --version): v0.14.0
• DNS provider: GCP
• Others:
  problem with recreate records absent in 0.13.5 and appeared in 0.13.6. Flag --txt-wildcard-replacement didn't help me.

[k8s-triage-robot]

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

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

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue 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.

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

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue 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.