Closed ismferd closed 2 years ago
@ismferd hey, What was the issue? Thinking about doing the same implementation
@tamirhad Sorry for the delay.
the thing this annotation:
--annotation-filter=kubernetes.io/ingress.class=alb
both controllers are listening this annotation, it means both will write an entry on route53.
If you want to get different behaviors you have to change this annotation
Describe the bug External DNS builds the ingress in both zones private and public. I have this kind of manifest, which creates entry in both zones:
Steps to reproduce We have 2 controllers of external dns, one for the public hosted zone and the other one for the private hosted zone:
Expected outcome I would like to create a new entry on route53 depending on the ingress annotation
alb.ingress.kubernetes.io/scheme:
Environment
Additional Context: