クラスタ外部に公開されている 2 つの Ingress ゲートウェイに静的 IP アドレスを作成することをおすすめします。
ゲートウェイ
説明
apigee-mart-istio-ingressgateway
MART サービスが管理プレーンとの通信に使用する Istio Ingress ゲートウェイ。
istio-ingressgateway
Message Processor ロードバランサが API プロキシ トラフィックを送受信するために使用する Istio Ingress ゲートウェイ。
これらのゲートウェイはロードバランサでプロビジョニングされます。デフォルトでは、このロードバランサの IP アドレスはエフェメラルになります。つまり、いずれかのサービスが削除され復元されると、新しいロードバランサの IP が取得されます。
このトピックでは、GKE と Anthos GKE（GKE On-Prem）にデプロイした Apigee ハイブリッドに静的 IP アドレスを定義する方法について説明します。
GKE で静的 IP アドレスを構成する
静的外部 IP アドレスの予約手順に沿って、2 つの静的 IP アドレスを作成します。アドレスには任意の名前を付けることができます（apigee-hybrid-mart、apigee-hybrid-runtime など）。完了すると、次のステップのクラスタ構成で使用される 2 つの IP 番号が作成されます（たとえば、35.225.131.189、34.66.75.196 など）。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-30 UTC。"],[[["\u003cp\u003eThis documentation is for Apigee hybrid version 1.1, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends using static IP addresses for the \u003ccode\u003eapigee-mart-istio-ingressgateway\u003c/code\u003e and \u003ccode\u003eistio-ingressgateway\u003c/code\u003e to prevent IP address changes upon service deletion and restoration.\u003c/p\u003e\n"],["\u003cp\u003eTo configure static IPs on GKE, reserve two static external IP addresses and add their values to the \u003ccode\u003eloadBalancerIP\u003c/code\u003e property in the \u003ccode\u003eingress\u003c/code\u003e component of your overrides file.\u003c/p\u003e\n"],["\u003cp\u003eTo configure static IPs on Anthos GKE, create two static IPs following the Anthos GKE instructions and then add their values to the \u003ccode\u003eloadBalancerIP\u003c/code\u003e property in the \u003ccode\u003eingress\u003c/code\u003e component of your overrides file.\u003c/p\u003e\n"],["\u003cp\u003eAfter updating your overrides file for either GKE or Anthos, apply the changes to your cluster using the \u003ccode\u003e-c istio\u003c/code\u003e flag, as only the \u003ccode\u003eistio\u003c/code\u003e component requires updates.\u003c/p\u003e\n"]]],[],null,["# Configure static IP addresses\n\n| You are currently viewing version 1.1 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nGoogle recommends that you create static IP addresses for the two ingress gateways that\nare exposed outside the cluster:\n\nThese gateways are provisioned with [load balancers](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer).\nBy default, the IP addresses for these load balancers are *ephemeral*. That\nmeans whenever one of the services is deleted and restored, it gets a new load balancer IP.\nThis topic explains how to define static IP addresses for Apigee hybrid deployed on GKE and Anthos GKE (GKE On-Prem).\n\n\u003cbr /\u003e\n\nConfigure static IP addresses on GKE\n------------------------------------\n\n1. Follow the instructions in [Reserving a static external IP address](https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address) to create two static IP addresses. You can give the addresses any name you wish, for example: `apigee-hybrid-mart` and `apigee-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.189` and `34.66.75.196`\n2. In your overrides file, add the following `loadBalancerIP` configurations to the ingress component: \n\n ### Syntax\n\n The configuration has the following structure and syntax.\n Values in \u003cvar translate=\"no\"\u003ered, bold italics\u003c/var\u003e are\n property values that you must provide: \n\n ```gdscript\n ingress:\n enableAccesslog: true\n runtime:\n loadBalancerIP: runtime_IP\n mart:\n loadBalancerIP: mart_IP\n ```\n\n ### Example\n\n The following example shows the completed configuration with example property values\n added: \n\n ```gdscript\n ingress:\n enableAccesslog: true\n runtime:\n loadBalancerIP: 35.225.131.189\n mart:\n loadBalancerIP: 34.66.75.196\n ```\n3. Apply your overrides file to the cluster. Because only the `istio`\n component needs to be updated, you can use the `-c istio` flag. For example:\n\n $APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio\n\nConfigure static IP addresses for Anthos GKE\n--------------------------------------------\n\n1. 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.189` and `34.66.75.196`\n2. Open your overrides file.\n3. Add the following configuration for `ingress`: \n\n ### Syntax\n\n The configuration has the following structure and syntax.\n Values in \u003cvar translate=\"no\"\u003ered, bold italics\u003c/var\u003e are\n property values that you must provide: \n\n ```gdscript\n ingress:\n enableAccesslog: true\n runtime:\n loadBalancerIP: runtime_IP\n mart:\n loadBalancerIP: mart_IP\n ```\n\n ### Example\n\n The following example shows the completed configuration with example property values\n added: \n\n ```gdscript\n ingress:\n enableAccesslog: true\n runtime:\n loadBalancerIP: 35.225.131.189\n mart:\n loadBalancerIP: 34.66.75.196\n ```\n4. Save the file.\n5. Apply your overrides file to the cluster. Because only the `istio`\n component needs to be updated, you can use the `-c istio` flag. For example:\n\n $APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio"]]
