This procedure describes adding additional Cloud Service Mesh gateways to your Apigee hybrid
installation.
Installing additional Cloud Service Mesh gateways
In the Cloud Service Mesh overlay.yaml file you can add more ingress gateways by
following a similar pattern as the one below. Note that the
spec.components[].label and spec.components[].k8s.service.selector
elements allow you to associate a named ingress gateway with a specific virtual host, as
explained in Targeting an ingress to a virtual host.
Follow the Cloud Service Mesh documentation for your platform to apply the changes.
Targeting an Cloud Service Mesh/istio ingress to a virtual host
You can target a labeled Cloud Service Mesh/istio ingress gateway to a specific virtual host in your overrides file.
This configuration specifies the ingress gateway where Apigee will apply the virtual host's configuration. In
the following example, traffic to virtual host milk-vh is directed through
the ingress labeled dairy and traffic to the other two virtual hosts goes through
the vegetables ingress. The ingresses must be properly labeled, as explained in
Installing additional Apigee ingress gateway gateways.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThis content explains how to add multiple Cloud Service Mesh ingress gateways to an Apigee hybrid installation using the \u003ccode\u003eoverlay.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003espec.components[].label\u003c/code\u003e and \u003ccode\u003espec.components[].k8s.service.selector\u003c/code\u003e elements in the \u003ccode\u003eoverlay.yaml\u003c/code\u003e file allow associating named ingress gateways with specific virtual hosts.\u003c/p\u003e\n"],["\u003cp\u003eTraffic can be routed to specific virtual hosts through designated ingress gateways by defining the \u003ccode\u003eselector\u003c/code\u003e property within the virtual host configuration in the overrides file.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid version 1.8 and later utilizes Apigee ingress gateway, and the process of configuring multiple instances of it is different from the described Cloud Service Mesh gateways.\u003c/p\u003e\n"],["\u003cp\u003eBy properly labeling the ingress gateways in the \u003ccode\u003eoverlay.yaml\u003c/code\u003e file and configuring the \u003ccode\u003eselector\u003c/code\u003e for each virtual host, you can control which ingress gateway handles the traffic for each virtual host.\u003c/p\u003e\n"]]],[],null,[]]