MART 서비스에서 관리 영역과 통신하는 데 사용되는 Istio 인그레스 게이트웨이입니다.
istio-ingressgateway
메시지 프로세서 부하 분산기를 통해 API 프록시 트래픽을 보내고 받는 데 사용되는 Istio 인그레스 게이트웨이입니다.
이러한 게이트웨이는 부하 분산기로 프로비저닝됩니다.
기본적으로 이러한 부하 분산기의 IP 주소는 일시적입니다. 즉, 서비스 중 하나가 삭제되고 복원될 때마다 새 부하 분산기 IP를 가집니다.
이 주제에서는 GKE 및 Anthos GKE(GKE On-Prem)에 배포된 Apigee Hybrid의 고정 IP 주소를 정의하는 방법을 설명합니다.
GKE에서 고정 IP 주소 구성
고정 외부 IP 주소 예약의 안내에 따라 고정 IP 주소 두 개를 만듭니다. 주소에 원하는 이름을 지정할 수 있습니다(예: apigee-hybrid-mart 및 apigee-hybrid-runtime). 완료되면 다음 단계에서 2개의 IP 번호를 클러스터 구성에 사용할 수 있습니다. 예를 들면 35.225.131.189 및 34.66.75.196입니다.
재정의 파일에서 다음 loadBalancerIP 구성을 인그레스 구성요소에 추가합니다.
구문
구성의 구조와 문법은 다음과 같습니다.
red, bold italics의 값은 제공해야 하는 속성 값입니다.
[[["이해하기 쉬움","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-09-05(UTC)"],[[["\u003cp\u003eThis document outlines the process of configuring static IP addresses for the \u003ccode\u003eapigee-mart-istio-ingressgateway\u003c/code\u003e and \u003ccode\u003eistio-ingressgateway\u003c/code\u003e in Apigee hybrid deployments on GKE and Anthos GKE.\u003c/p\u003e\n"],["\u003cp\u003eStatic IP addresses are recommended for these gateways to prevent IP changes when services are deleted and restored, as default load balancer IPs are ephemeral.\u003c/p\u003e\n"],["\u003cp\u003eTo configure static IPs on GKE, users need to reserve two static external IP addresses and then add the \u003ccode\u003eloadBalancerIP\u003c/code\u003e configurations to their overrides file under the \u003ccode\u003eingress\u003c/code\u003e component, specifying each IP for \u003ccode\u003eruntime\u003c/code\u003e and \u003ccode\u003emart\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eFor Anthos GKE, the process involves creating two static IP addresses according to Anthos GKE documentation, then adding the corresponding \u003ccode\u003eloadBalancerIP\u003c/code\u003e configurations to the overrides file for \u003ccode\u003eruntime\u003c/code\u003e and \u003ccode\u003emart\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAfter setting up the IPs in the overrides file for GKE and Anthos, use the \u003ccode\u003e$APIGEECTL_HOME/apigeectl init -f my-overrides.yaml -c istio\u003c/code\u003e command to apply these changes.\u003c/p\u003e\n"]]],[],null,["# Configure static IP addresses\n\n| You are currently viewing version 1.2 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"]]
