v0.14.0 don't support arg --oci-zone-scope=

[RuanCarvalh]

What happened:

the argument "--oci-zone-scope=" is not published in version v0.14.0 in the documentation for OCI, its use is recommended for this version: https://github.com/kubernetes-sigs/external-dns/blob/ master/docs/tutorials/oracle.md

However, we don't have it created: https://github.com/kubernetes-sigs/external-dns/blob/raffo/kustomize-v0.14.0/provider/oci/oci_test.go

When trying to use it we received the invalid file error

What you expected to happen:

In the master branch it is created: https://github.com/kubernetes-sigs/external-dns/blob/master/provider/oci/oci_test.go
I think there was some merge missing

How to reproduce it (as minimally and precisely as possible):
Deploy external DNS on v0.14.0 using --oci-zone-scope=GLOBAL or --oci-zone-scope=PRIVATE

Environment:

• External-DNS version 0.14.0
• DNS provider: OCI

[dongjiang1989]

This feature is in the main branch, not in the v0.14.0 tag.

[RuanCarvalh]

This feature is in the main branch, not in the v0.14.0 tag.

Yes, I understand, but in the documentation it is recommended to use version 0.14.0 to use this feature, but it is not available, would you know which version I should use to have the feature?

[wellwanger]

Hi @RuanCarvalh! in my research this feature was merged to master recently by PR #3995 so I understand that it will available in next release of the project.

[benarnold42]

It looks like the only thing missing is the next release. Any idea when this might happen?

[omidizadkhasti]

Hi @wellwanger, is there any update when this features will available. and is there any workaround to use this feature in our environment (by pull mater and build the image)?

[wellwanger]

Hi @omidizadkhasti, I am not a member of this project so I don`t have info about next release date. What I can say is that as a temporary solution you could use a fork of dns external available at project Verrazzano (Open source project curated by Oracle) which already has this feature available. https://github.com/verrazzano

[k8s-triage-robot]

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

This bot triages un-triaged 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:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged 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:

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

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

/lifecycle rotten

[wizbe97]

it is worth noting that for OCI, the --oci-zone-scope flag does not actually work, in the 0.14.2 image version.

I have to set it to --oci-zone-scope= rather to work in my zones, setting --oci-zone-scope=PRIVATE does not create any records

[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-sigs/prow repository.

[wellwanger]

/remove-lifecycle stale