Research Spike for Istio Egressgateways

Research effort to test an egressgateway in Istio...

Modified line 781 of the k3d-dev.sh script from:

          - {key: app, operator: In, values: [passthrough-ingressgateway]}

to:

          - {key: app, operator: In, values: [istio-egressgateway]}

So that the 2nd IP in AWS is provided to Istio for the egress gateway when the script is executed like:

./docs/assets/scripts/developer/k3d-dev.sh -a -b -w 

Deployed with Istio like this:

istio:
  enabled: true
  values:
    egressGateways:
      # -- This key becomes the name of the egressGateway
      istio-egressgateway:
        enabled: true
        k8s:
          service:
            # -- "LoadBalancer" or "NodePort"
            type: "LoadBalancer"    

Which brings up a cluster with an Istio egressgateway pod (that can be assigned a specific node affinity).