-
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
OCI Private DNS zone management #2326
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
I have create a PR for this some time ago. Unfortunatally haven't been able to get this merged for various reasons. In the mean time: |
Same issue here, would be awesome to get this fixed |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle rotten |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What happened:
Hi there, I'm running external-dns witj OCI provider on dry-run mode for now.
When the pod start, it does not found any zone on OCI. The fact is that we have plenty of DNS zone, but only private zone attached to private view.
The logs are:
No zones found in compartment "ocid1.compartment.oci..............."
There is no error logs at all, everything seems to work properly, I can see in logs that the pod will add many records if not running in dry-run mode.
But those ADD operations appears in warning logs because it can't find any matching zone (but the target zone does exists)
level=warning msg="No matching zone for record operation { Domain=cb-cluster-tst-grc-0001.k8s......... RecordHash=<nil> IsProtected=<nil> Rdata=172.29.145.148 RrsetVersion=<nil> Rtype=A Ttl=300 Operation=ADD }"
What you expected to happen:
We expect that the pod to be able to find those private zone in order to add records in it.
How to reproduce it (as minimally and precisely as possible):
To reproduce this bug I think you simply have to run a pod linked to an oci environment which got private dns zone linked to it.
Anything else we need to know?:
Environment:
external-dns --version
):external-dns --version return blank line, I'm running image k8s.gcr.io/external-dns/external-dns:v0.9.0
The text was updated successfully, but these errors were encountered: