CNAME+TXT on GCP fails

[howardjohn]

What happened:

I set up external-dns with Gateway API and GCP DNS. I get these logs:

{"level":"info","msg":"Change zone: howardjohn-net batch #0","time":"2023-08-21T17:15:05Z"}
{"level":"info","msg":"Add records: cname-echo.mesh.howardjohn.net. TXT [\"heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=httproute/server/echo\"] 300","time":"2023-08-21T17:15:05Z"}
{"level":"info","msg":"Add records: echo.mesh.howardjohn.net. CNAME [gateway-istio.server.svc.cluster.local.] 300","time":"2023-08-21T17:15:05Z"}
{"level":"info","msg":"Add records: echo.mesh.howardjohn.net. TXT [\"heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=httproute/server/echo\"] 300","time":"2023-08-21T17:15:05Z"}
{"level":"fatal","msg":"googleapi: Error 400: The resource record set 'entity.change.additions[echo.mesh.howardjohn.net.][CNAME]' is invalid because the DNS name 'echo.mesh.howardjohn.net.' has a resource record set of the type 'TXT'. A DNS name may have either one CNAME resource record set or resource record sets of other types, but not both.\nMore details:\nReason: cnameResourceRecordSetConflict, Message: The resource record set 'entity.change.additions[echo.mesh.howardjohn.net.][CNAME]' is invalid because the DNS name 'echo.mesh.howardjohn.net.' has a resource record set of the type 'TXT'. A DNS name may have either one CNAME resource record set or resource record sets of other types, but not both.\nReason: cnameResourceRecordSetConflict, Message: The resource record set 'entity.change.additions[echo.mesh.howardjohn.net.][TXT]' is invalid because the DNS name 'echo.mesh.howardjohn.net.' has a resource record set of the type 'TXT'. A DNS name may have either one CNAME resource record set or resource record sets of other types, but not both.\n","time":"2023-08-21T17:15:05Z"}

My Gateway address is a Hostname type.

If I change the Gateway to an IP address type it works fine

What you expected to happen:

DNS is setup correctly

Environment:

• External-DNS version (use external-dns --version): v0.13.5
• DNS provider: GCP
• Others:

[rwunderer]

EDIT: sorry, missed that this has already been addressed.

Duplicate of #262

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