We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello
Can you confirm the logic behind the creation of dns records when source=pods?
At the moment we have in the flag source=pod With a fqdn template {name}
And we get the log message Stating if hostNetwork=false skips the dns record creation
And we see this on the code
https://github.com/kubernetes-sigs/external-dns/blob/master/source/pod.go#L87
Can we use annotations to force the pods to have a dns record created?
The text was updated successfully, but these errors were encountered:
It seems that this behavior is controlled by ExternalDNS , and the requirement is being addressed here kubernetes-sigs/external-dns#3174
Sorry, something went wrong.
No branches or pull requests
Hello
Can you confirm the logic behind the creation of dns records when source=pods?
At the moment we have in the flag source=pod
With a fqdn template {name}
And we get the log message
Stating if hostNetwork=false skips the dns record creation
And we see this on the code
https://github.com/kubernetes-sigs/external-dns/blob/master/source/pod.go#L87
Can we use annotations to force the pods to have a dns record created?
The text was updated successfully, but these errors were encountered: