OCI provider: failed to add record for private zone in oracle cloud

[vickydev90]

What happened:
When trying to add records in private zone in compartment, externaldns for oci fails to add record and gives warnings

time="" level=warning msg="No zones in compartment \"ocid1.compartment.oc1..\" match domain filters [xyz.com]"
time="" level=warning msg="No zones in compartment \"ocid1.compartment.oc1..\" match domain filters [xyz.com]"
time="" level=warning msg="No matching zone for record operation { Domain=abc.xyz.com RecordHash=<nil> IsProtected=<nil> Rdata=1.2.3.4 RrsetVersion=<nil> Rtype=A Ttl=300 Operation=ADD }"

What you expected to happen:
Add A record in private zone as provided by domain filter

How to reproduce it (as minimally and precisely as possible):
setup latest external-dns for OCI provider and specify compartment id where private zone xyz.com is created
create ingress/service with annotation of external dns matching domain filter(xyz.com).

for eg. Annotations: external-dns.alpha.kubernetes.io/hostname: abc.xyz.com

Environment:

• External-DNS version (use external-dns --version): 0.10.2
• DNS provider: OCI

[mschmidt291]

@vickydev90 Any plans on fixing the PR? We also experience this issue.
Thanks in advance

[NoNalTrX]

Same issue here, private zone are not found by external dns.

tried with and without domain filter flag

No zones in compartment "ocid1.compartment.oc1..aaaa....." match domain filters...."

Any chance to get this fixed?

[jlamillan]

Any thoughts @prydie?

[vickydev90]

i have raised PR for review, this would give option for private zones filter.

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[benarnold42]

/remove-lifecycle stale

[buramundo]

Hi, any news about this "crutial" feature to my OCI Cloud K8S Infrastructure ..... Sorry to insist

[buramundo]

UP : Any information about this request ?

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.

[benarnold42]

/reopen /remove-lifecycle rotten

[mshekharee]

Does this support to create records in oracle private zone?

[anders-swanson]

Should be fixed by #3995