<p>I am trying to route outbound traffic from an application in my GKE cluster through a static IP, as the destination server requires whitelisting IP for access. I have been able to do this using the terraformed nat gateway, but this impacts all traffic from the cluster.</p>

<p>Following the istio guide on the site, I've been able to route traffic through an egressgateway pod (I can see it in the gateway logs), but I need the gateway to have a static ip, and there is no override in the helm values for egressgateway static ip.</p>

<p>How can I assign a static ip to the egressgateway without having to patch anything or hack it after installing istio?</p>

<p>I think of your problem as having three steps. First, to fix the outgoing traffic to a particular pod.  The istio egress gateway does this for you.  Second and third, to fix the pod to a particular IP address.</p>

<p>If you use GCP's version of floating IP addresses, then you can assign a known IP to one of the hosts in your cluster. Then, use node affinity on the egress-gateway to schedule it to the particular host, <a href="https://kubernetes.io/docs/concepts/configuration/assign-pod-node/" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</a></p>

<p>I've edited the egress deployment in one of my test clusters, to 
<code>
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - amd64
                - ppc64le
                - s390x
              - key: kubernetes.io/hostname
                operator: In
                values:
                - worker-2720002
</code>
to pin it by the hostname label, but you'll probably want to choose and apply a new label to the node when you assign it a floating ip.  In my test, the pod is moved to the specified node, and my outgoing egress traffic does too.</p>
