Google recommends that you create static IP addresses for the two ingress gateways that are exposed outside the cluster:
| Gateway | Description | 
|---|---|
| apigee-mart-istio-ingressgateway | The Istio ingress gateway used by the MART service to communicate with the management plane. | 
| istio-ingressgateway | The Istio ingress gateway used to send and receive API proxy traffic by the message processor load balancers. | 
These gateways are provisioned with load balancers. By default, the IP addresses for these load balancers are ephemeral. That means whenever one of the services is deleted and restored, it gets a new load balancer IP.
This topic explains how to define static IP addresses for Apigee hybrid deployed on GKE and Anthos GKE (GKE On-Prem).Configure static IP addresses on GKE
- 
 Follow the instructions in 
  Reserving a static external IP address to create
  two static IP addresses. You can give the addresses any name you wish, for example:
  apigee-hybrid-martandapigee-hybrid-runtime. When you finish, you will have two IP numbers to use in the cluster configuration in the next step. For example:35.225.131.189and34.66.75.196
- In your overrides file, add the following loadBalancerIPconfigurations to the ingress component:SyntaxThe configuration has the following structure and syntax. Values in red, bold italics are property values that you must provide: ingress: enableAccesslog: true runtime: loadBalancerIP: runtime_IP mart: loadBalancerIP: mart_IP ExampleThe following example shows the completed configuration with example property values added: ingress: enableAccesslog: true runtime: loadBalancerIP: 35.225.131.189 mart: loadBalancerIP: 34.66.75.196 
- Apply your overrides file to the cluster. Because only the - istiocomponent needs to be updated, you can use the- -c istioflag. For example:- $APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio
Configure static IP addresses for Anthos GKE
- 
 Refer to the Anthos GKE documentation and create two static IP addresses by following the
    Anthos GKE specific instructions. When you finish, you
  will have two IP numbers to use in the cluster configuration in the next step. For example:
  35.225.131.189and34.66.75.196
- Open your overrides file.
- Add the following configuration for ingress:SyntaxThe configuration has the following structure and syntax. Values in red, bold italics are property values that you must provide: ingress: enableAccesslog: true runtime: loadBalancerIP: runtime_IP mart: loadBalancerIP: mart_IP ExampleThe following example shows the completed configuration with example property values added: ingress: enableAccesslog: true runtime: loadBalancerIP: 35.225.131.189 mart: loadBalancerIP: 34.66.75.196 
- Save the file.
- Apply your overrides file to the cluster. Because only the - istiocomponent needs to be updated, you can use the- -c istioflag. For example:- $APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio