External-dns functioning with the ingressClassName field in the new ingress(Nginx Controller) resource

[jeswinkninan]

External-dns functioning with the ingressClassName field in the new ingress(Nginx Controller) resource

What would you like to be added:

From the types: https://github.com/kubernetes-sigs/external-dns/blob/master/pkg/apis/externaldns/types.go, I can see the flags related to filter the processing sources are annotation-filter, label-filter. So I am looking here to find how the external-dns functioning with the ingressClassName field in the new ingress(Nginx Controller) resource in newer version instead of the value given as annotation in the previous ingress configurations. Is this a new feature request or something which I need to follow to use the existing feature.

Why is this needed:

[jeswinkninan]

Ref: https://github.com/kubernetes-sigs/external-dns/blob/master/source/ingress.go

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[Diaoul]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.

[mattmichal]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@mattmichal: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen
/remove-lifecycle rotten

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.

[aojea]

/reopen

This was reported in kubernetes/kubernetes kubernetes/kubernetes#115018

The annotation was deprecated in Ingress v1beta1 and moved to field in v1. Ingress v1beta1 has been totally deprecated and is no longer served in kubernetes since 1.22, so the controller should move to the field to be compatible

[k8s-ci-robot]

@aojea: Reopened this issue.

In response to this:

/reopen

This was reported in kubernetes/kubernetes kubernetes/kubernetes#115018

The annotation was deprecated in Ingress v1beta1 and moved to field in v1. Ingress v1beta1 has been totally deprecated and is no longer served in kubernetes since 1.22, so the controller should move to the field to be compatible

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.

[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

[szuecs]

/close by merging #3589

[sergeyshevch]

@szuecs Is it possible to create a release with this feature? Looks like many people waiting for it

[szuecs]

@sergeyshevch I have not the power to release and even better no idea how to do it.

[visit1985]

@szuecs Is it possible to create a release with this feature? Looks like many people waiting for it

@Raffo do you have insight on the release schedule? Can you maybe answer @sergeyshevch's question?