> [!CAUTION]
> You are currently viewing version 1.8 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions).

<button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">Version 1.8 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/migrating-to-apigee-ingress.md.txt)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/migrating-to-apigee-ingress.md.txt)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/migrating-to-apigee-ingress.md.txt)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/migrating-to-apigee-ingress.md.txt)
- [List of supported versions](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt#supported-versions)
- Unsupported versions:
- [v1.13](https://docs.cloud.google.com/apigee/docs/hybrid/v1.13/migrating-to-apigee-ingress.md.txt)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/migrating-to-apigee-ingress.md.txt)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/migrating-to-apigee-ingress.md.txt)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/migrating-to-apigee-ingress.md.txt)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/migrating-to-apigee-ingress.md.txt)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/migrating-to-apigee-ingress.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/migrating-to-apigee-ingress.html)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/migrating-to-apigee-ingress.html)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/migrating-to-apigee-ingress.html)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/migrating-to-apigee-ingress.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/migrating-to-apigee-ingress.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/migrating-to-apigee-ingress.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/migrating-to-apigee-ingress.html)


Use this procedure to migrate existing Apigee hybrid v1.8 installations from using
Anthos Service Mesh for ingress to using Apigee ingress gateway.

## Apigee ingress gateway in Apigee hybrid version 1.8


Starting in version 1.8, Apigee hybrid offers a new feature to manage the ingress gateway for
your hybrid installation, *Apigee ingress gateway*. Anthos Service Mesh is no longer a
prerequisite for hybrid installation and Apigee will stop supplying routing configuration to
Anthos Service Mesh. After the upgrade, you have to migrate the traffic to the new Apigee ingress gateway
gateway.


Two scenarios for migrating are:

- **Multi-cluster or multi-region migration** (recommended):

  Before switching to a new Ingress for Apigee, drain all the traffic to another cluster or
  region from the cluster you are migrating. This will give you time to test if the new
  Apigee ingress gateway gateway is working as expected. Then shift the traffic back to the upgraded
  cluster.
- **In-place upgrade** (not recommended in production environments):

  During the upgrade Apigee will bring up the new ingress gateway with a new IP address.
  You can then test if the new Apigee ingress gateway gateway is working as expected, and then shift
  traffic to the new ingress. There might be downtime during this upgrade.

## Install Apigee ingress gateway

1. To install Apigee ingress gateway, you need to add the [`ingressGateways`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways) property to your overrides file.

   ### Syntax

   ```
   ingressGateways:
   - name: INGRESS_NAME
     replicaCountMin: REPLICAS_MIN
     replicaCountMax: REPLICAS_MAX
     resources:
       requests:
         cpu: CPU_COUNT_REQ
         memory: MEMORY_REQ
       limits:
         cpu: CPU_COUNT_LIMIT
         memory: MEMORY_LIMIT
     svcAnnotations:  # optional.
       SVC_ANNOTATIONS_KEY: SVC_ANNOTATIONS_VALUE
     svcLoadBalancerIP: SVC_LOAD_BALANCER_IP # optional
   ```

   ### Example

   ```
   ingressGateways:
   - name: prod1
     replicaCountMin: 2
     replicaCountMax: 100
     resources:
       requests:
         cpu: 1
         memory: 1Gi
       limits:
         cpu: 2
         memory: 2Gi
     svcAnnotations:  # optional. See Known issue 243599452.
       networking.gke.io/load-balancer-type: "Internal"
     svcLoadBalancerIP: 198.252.0.123 
   ```
   - <var translate="no">INGRESS_NAME</var> is the name of the ingress deployment. This can be any name that meets the following requirements:
     - Have a maximum length of 17 characters
     - Contain only lowercase alphanumeric characters, '-' or '.'
     - Start with an alphanumeric character
     - End with an alphanumeric character

     See [`ingressGateways[].name`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-name) in the Configuration property reference.
   - <var translate="no">REPLICAS_MIN</var> and <var translate="no">REPLICAS_MAX</var> are the minimum and maximum replica counts for Apigee ingress gateway in your installation. For more information and default settings, see [`ingressGateways[].replicaCountMin`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-replicacountmin) and [`ingressGateways[].replicaCountMax`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-replicacountmax) in the Configuration property reference.
   - <var translate="no">CPU_COUNT_REQ</var> and <var translate="no">MEMORY_REQ</var> are the CPU and memory request for each replica of Apigee ingress gateway in your installation.

     > [!NOTE]
     > Set these properties if you have previously set them for your Anthos Service Mesh ingress gateway, for example in your `overlay.yaml` file.


     For more information and default settings, see
     [`ingressGateways[].resources.requests.cpu`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-resources-requests-cpu)
     and
     [`ingressGateways[].resources.requests.memory`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-resources-requests-memory)
     in the Configuration property reference.
   - <var translate="no">CPU_COUNT_LIMIT</var> and <var translate="no">MEMORY_LIMIT</var> Are the maximum CPU and memory limits for each replica of Apigee ingress gateway in your installation.

     > [!NOTE]
     > Set these properties if you have previously set them for your Anthos Service Mesh ingress gateway, for example in your `overlay.yaml` file.


     For more information and default settings, see
     [`ingressGateways[].resources.limits.cpu`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-resources-limits-cpu)
     and
     [`ingressGateways[].resources.limits.memory`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-resources-limits-memory)
     in the Configuration property reference.
   - <var translate="no">SVC_ANNOTATIONS_KEY</var> <var translate="no">SVC_ANNOTATIONS_VALUE</var> (optional):

     > [!NOTE]
     > **Note:** The `ingressGateways[].svcAnnotations` field in `overrides.yaml` is not working as expected. See [Known issue 243599452](https://docs.cloud.google.com/apigee/docs/release/known-issues.md.txt#243599452)


     This is a key-value pair that provides
     annotations for your default ingress service. Annotations are used by your cloud platform to
     help configure your hybrid installation, for example setting the loadbalancer type to
     either internal or external. For example:

     ```
     ingressGateways:
       svcAnnotations:
         networking.gke.io/load-balancer-type: "Internal"
     ```

     Annotations vary from platform to platform. Refer to your platform
     documentation for required and suggested annotations.

     > [!NOTE]
     > **Note:** You do not need to set `Annotations` if you are creating your own Kubernetes service for ingress deployment as documented in [Expose Apigee ingress gateway](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-expose-apigee-ingress.md.txt).

     See [`ingressGateways[].svcAnnotations`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-svcannotations) in the Configuration property reference.
   - <var translate="no">SVC_LOAD_BALANCER_IP</var> (optional) Allows you to assign a static IP address for your load balancer. On platforms that support specifying the load balancer IP address, the load balancer will be created with this IP address. On platforms that do not allow you to specify the load balancer IP address, this property is ignored.

     If you do not have a static IP address allocated for your load balancer, leave this property
     out of your overrides file.

     > [!CAUTION]
     > **Caution:** Make sure not to specify the same IP address as the current istio-ingressgateway. This could cause problems while that service is still on the cluster.

     > [!NOTE]
     > **Note:** You do not need to set `LoadBalancerIP` if you are creating your own Kubernetes service for ingress deployment as documented in [Expose Apigee ingress gateway](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-expose-apigee-ingress.md.txt).

     See [`ingressGateways[].svcLoadBalancerIP`](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/config-prop-ref.md.txt#ingressgateways-svcloadbalancerip) in the Configuration property reference.
2. Apply the changes to install Apigee ingress gateway with the following commands:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides/overrides.yaml
   ```

## Switch traffic to Apigee ingress gateway


To migrate traffic from Anthos Service Mesh to Apigee ingress gateway follow the steps in
[Switch traffic from Anthos Service Mesh to Apigee ingress gateway](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/upgrade.md.txt#switch-to-ingress)
in the Upgrading to Apigee Hybrid v1.8 topic.