Closed davhdavh closed 1 week ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I would submit a PR, if anyone could point me in the right direction
I'm getting the same error. @jacobbednarz maybe you could help?
i'm sorry but this lacks enough information for me as an outsider to be able to debug the issue. in general though, this API error points at the payload you have provided in not valid for the record type you requested. what do the HTTP interactions look like here?
in general though, this API error points at the payload you have provided in not valid for the record type you requested.
I guess that the MX records are passed as 10 sub.site.com
in the Content
field: https://github.com/kubernetes-sigs/external-dns/blob/fa17f9d06cbfe3315430529151324fae5a421e43/provider/cloudflare/cloudflare.go#L446 and the fix is that it needs to be passed as multiple/different arguments?
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/reopen
@james-callahan: You can't reopen an issue/PR unless you authored it or you are a collaborator.
/reopen
@davhdavh: Reopened this issue.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
What happened:
What you expected to happen:
Mx was created.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
TXT for DKIM using DNSEndpoint, A for ingress, TXT for SPF using DNSEndpoint all work just fine, so problem is specific to MX. Manually creating record in cloudflare UI works.
Environment:
external-dns --version
): 'registry.k8s.io/external-dns/external-dns:v0.13.6'