-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
CloudFlare provider continuously recreates apex records #4720
Comments
I've been around this repository long enough and this crops up time-to-time :) If you don't already, I'd set a Deployment strategy to avoid duplicate Pods or switch to ReplicaSet. |
Ah, no, I’m using Traefik. Good to know, though!
|
oh, that second part of your comment didn't come in the email. Where would you recommend setting that configuration? |
Set the Deployment strategy to Recreate to avoid duplicate Pods, see this repositories' helm chart configuration for example. |
oh, I see. It's already set to that. This doesn't seem to be a Kubernetes object thing, but the behavior of external-dns within the pod. |
That's 1 less thing to worry about. Some findings that may be helpful:
relevant in that both Issue Authors are using I'm not utilizing |
What happened: I have external-dns configured to source from ingresses. This works wonderfully, and all the records get created. However, it updates records for the domain apexes on every run, saying that no hosted zone matches.
What you expected to happen: I expected that external-dns would not change any records that already exist and are in the correct state without filtering out apex-level A records.
How to reproduce it (as minimally and precisely as possible):
The minimum I can find is adding an annotation pointing to a bare domain, then running external-dns in the following configuration:
Each update cycle looks like this (changing my domain to be
example.com
, for clarity):(Worth noting that I do expect to have three IPs for each name; that's fine.)
Anything else we need to know?: Nope, I don't think so!
Environment:
external-dns --version
): 0.14.2The text was updated successfully, but these errors were encountered: