enable a dynamic target lookup

[mabels]

Added the a annotation to ingressroute to enable a dynamic target lookup

switchboard.borchero.com/target

1. a comma seperated list of ip number ipv4 ipv6 [1.1.1.1,1::1]
2. one domain name [cname.example.cname]
3. service key like k8snamespace/svcname or svcname than the
   integrations.externalDNS.targetService.namespace is used

[borchero]

Thanks a lot for your contribution @mabels! I briefly skimmed over it and left two comments.

In general, I would appreciate if you could give some more context regarding the motivation behind this PR. Once I know what problem you're trying to solve, I'll be able to do a more proper review.

[mabels]

My motivation to this fix came from the following setup:

one ingress controller with two nlb why two:

The external is used for the external endpoints and the internal is used my internalone.
Both are getting names from aws so i have to the possibiliy to write two ingressroutes which are using different services to identify there targets.

[AmilcarM11]

My motivation to this fix came from the following setup:

one ingress controller with two nlb why two:

The external is used for the external endpoints and the internal is used my internalone. Both are getting names from aws so i have to the possibility to write two ingressroutes which are using different services to identify there targets.

Hello, I'm interested in this exact behavior.

Is there any chance of this PR to be merged?