External-dns: feature request: allow external dns to filter on a list of annotations
We have the scenario where we use ingress-class for ingresses associated with internal ingress but also a couple of other LoadBalancer services that do not go through the ingress. It would have been very nice and clean if the service has its own annotation and ingresses their own and then external dns would filter them both, rather then having to come up with other scenarios. We were able to find multiple scenarios to make it work but none of them was as nice and clean as having multiple annotations filtered in --annotation-filter argument (or a similar new argument)
GAHila
All 6 comments
+1! I would envision a logical inclusive OR of each --annotation-filter value.
This could be taken a step further by modifying --annotation-filter to accept an array of values that are logical ANDs such that you could chain filters to form composites by ANDing and ORing arbitrary annotations.
iAnomaly
on 8 Oct 2018
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
on 26 Apr 2019
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
fejta-bot
on 26 May 2019
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-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 25 Jun 2019
@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-testing, kubernetes/test-infra and/or fejta.
/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.
k8s-ci-robot
on 25 Jun 2019
I recently came across a use case for this sort of scenario. So would like to reopen this, as it would be helpful to allow for multiple possible ingress classes to leverage the same external-dns instance. Right now I have two instances, one for a private hosted zone, and one for a public hosted zone. Trying to have some other layers of isolation, but running an external-dns pod per ingress class seems overkill.
streetmapp
on 10 Jul 2019
Related issues
deimosfr
路
3Comments
linki
路
4Comments
Gnnng
路
3Comments
lemaral
路
4Comments
szuecs
路
4Comments
Most helpful comment
I recently came across a use case for this sort of scenario. So would like to reopen this, as it would be helpful to allow for multiple possible ingress classes to leverage the same external-dns instance. Right now I have two instances, one for a private hosted zone, and one for a public hosted zone. Trying to have some other layers of isolation, but running an external-dns pod per ingress class seems overkill.