-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't update Cloudflare records after update to 0.15.1 #5035
Comments
Are you using API token or CF_API_KEY and CF_API_EMAIL? It could be quite sensitive, but are there any useful debug logs? |
We are having the same issue. We are using CF_API_TOKEN. In the output there is not much information:
|
+1 here Also using |
/help |
@ivankatliarchuk: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
Share config that is failing. Is it helm or raw manifests? For those who know how to execute go, worth to try
export CF_API_TOKEN=xxxxxxxx
|
As well we have official staging images available for testing https://console.cloud.google.com/gcr/images/k8s-staging-external-dns/GLOBAL/external-dns?pli=1&inv=1&invt=AboC3A Coud someone give it a try? |
The image gcr.io/k8s-staging-external-dns/external-dns:v20250128-v0.15.1-142-g9619e6b1 still fails with the same error from above. It doesn't output anything more related to that change when using log-level=debug. We are also using the CF_API_TOKEN
|
@lcapka @0x77dev @stefanandres Can you grant your Cloudflare Token to have |
@AndrewCharlesHay already tried, did not work for me |
It works for me, but I'm not using a stock helm chart. Could someone share arguments, minimal config I'll try to dig a bit more. |
I think the version upgrade from 0.15.0 to 0.15.1 might be a red herring, instead maybe it's related to the issues described here? @stefanandres if you downgrade external-dns back to 0.15.0 does the issue remain? |
Down grading mine to 1.15.0 fixed it for me. |
Ignore me then 😆 I haven't had any problems using 0.15.0 or 0.15.1 with an API token with the correct scopes. |
Was the helm chart downgraded or only the image? |
I upgraded both, both downgrading the image only fixes the error. |
Trying with this staging image gives me this output:
Looks like it's specifically failing at the apex record which is a (flattened) CNAME for my CF tunnel. Here's the values.yaml I'm using with the v1.15.1 helm chart:
And the associated TXT record contents: |
@stefanandres Are you saying you had to downgrade the image and the Helm chart for it to work? |
I also encountered this issue on updating the apex record. In my case it is an A record. Downgrading to 1.15.0 fixed it. |
What happened:
After updating from 0.15.0 to 0.15.1 updating CF records just fails with "forbidden", even though nothing else changed.
Updating records after downgrading works again.
What you expected to happen:
It should update the record
This might be related to changes in:
But I can't find anything obvious.
The text was updated successfully, but these errors were encountered: