External-dns: multiple - --istio-ingress-gateway

[naveeng68]

Hi,
I am using two istio ingress load balancer (abc, xyz)
few services point to abc and few on xyz,
I created two my external Deployment.yaml
is like

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: external-dns
  namespace: ingress-support
  labels:
    app: external-dns
spec:
  selector:
    matchLabels:
      app: external-dns
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: external-dns
    spec:
      serviceAccountName: external-dns
      containers:
      - name: external-dns
        image: registry.opensource.zalan.do/teapot/external-dns
        args:
        - --source=service
        - --source=ingress
        - --source=istio-gateway
        - --domain-filter=****.net
        - --domain-filter=****.com
        - --provider=aws
        - --policy=upsert-only # would prevent ExternalDNS from deleting any records, omit to enable full synchronization
        - --registry=txt
        - --txt-owner-id=cluster.net

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: external-dns-xca
  namespace: ingress-support
  labels:
    app: external-dns-xca
spec:
  selector:
    matchLabels:
      app: external-dns
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: external-dns
    spec:
      serviceAccountName: external-dns
      containers:
      - name: external-dns
        image: registry.opensource.zalan.do/teapot/external-dns
        args:
        - --source=service
        - --source=ingress
        - --source=istio-gateway
        - --istio-ingress-gateway=istio-system/istio-ingressgateway-xca
        - --domain-filter=***.net
        - --domain-filter=***.com
        - --provider=aws
        - --policy=upsert-only # would prevent ExternalDNS from deleting any records, omit to enable full synchronization
        - --registry=txt
        - --txt-owner-id=cluster.net



md5-f846ac46d27ae033eaca7a9d838c5586



apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: test-service1
  annotations:
   ingress.kubernetes.io/force-ssl-redirect: "true"
   kubernetes.io/ingress.class: "istio-gateway"
spec:
  selector:
    istio: ingressgateway     #ingressgateway # use istio default controller
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - ***.net
    - ***.com



md5-162e2084706229081f5b88579670045a



apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: test-service2
  annotations:
   ingress.kubernetes.io/force-ssl-redirect: "true"
   kubernetes.io/ingress.class: "istio-gateway"
spec:
  selector:
    istio: ingressgateway     #ingressgateway # use istio default controller
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - ***.net
    - ***.com

both point to same load balancer either abc or xyz (which one is running later )
I need seprate service running on seprate load balancer.
Please guide me or do needful.

[amarrella]

Kinda similar to #757. I'm trying to tackle it in #758 but any help is more than welcome :)

[callum-p]

+1. I have a private gateway (AWS internal ELB) and a public gateway (public ELB) that I want to support.

[vinicius-xavier-ifood]

+1. Same above

[sujithvs74]

+1. Same above