-
Notifications
You must be signed in to change notification settings - Fork 33
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
Azure Private DNS handling #197
Comments
@git001: there is a documentation gap for the support of the private Azure zones indeed. From the API point of view, it's still the same provider: |
@alebedev87 thank you for the Update. I will test and write here what I have done and if it was working or not 😄 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
@jmanthei : can you please file a bug for the doc gap about private Azure DNS zones? |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
This PR suggest that it's possible to manage also azure private dns zones with external-dns-operator (edo).
https://github.com/openshift/external-dns-operator/pull/89/files
When I run this command with the latest edo can I also see some private dns output.
In the official doc is this not documented. Is the azure private DNS "just" not supported but possible or not available in the operator?
https://docs.openshift.com/container-platform/4.13/networking/external_dns_operator/nw-creating-dns-records-on-azure.html
What I understand in the CRD is the Azure private DNS not listed, right?
https://github.com/openshift/external-dns-operator/blob/release-4.13/bundle/manifests/externaldns.olm.openshift.io_externaldnses.yaml#L228
The text was updated successfully, but these errors were encountered: