> [!CAUTION]
> You are currently viewing version 1.7 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.7 (unsupported)</button>

- Supported versions:
- [v1.17 (latest)](https://docs.cloud.google.com/apigee/docs/hybrid/v1.17/install-asm.html)
- [v1.16](https://docs.cloud.google.com/apigee/docs/hybrid/v1.16/install-asm.html)
- [v1.15](https://docs.cloud.google.com/apigee/docs/hybrid/v1.15/install-asm.html)
- [v1.14](https://docs.cloud.google.com/apigee/docs/hybrid/v1.14/install-asm.html)
- [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/install-asm.html)
- [v1.12](https://docs.cloud.google.com/apigee/docs/hybrid/v1.12/install-asm.html)
- [v1.11](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-asm.html)
- [v1.10](https://docs.cloud.google.com/apigee/docs/hybrid/v1.10/install-asm.html)
- [v1.9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.9/install-asm.html)
- [v1.8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/install-asm.md.txt)
- [v1.7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-asm.md.txt)
- [v1.6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.6/install-asm.md.txt)
- [v1.5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.5/install-asm.md.txt)
- [v1.4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/install-asm.html)
- [v1.3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.3/install-asm.html)
- [v1.2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.2/install-asm.html)
- [v1.1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.1/install-asm.html)

## Install ASM


Apigee hybrid uses the Istio distribution provided with Anthos Service Mesh (ASM).
Follow these steps to install ASM in your cluster.


### Supported ASM versions


See [Apigee hybrid: supported platforms](https://docs.cloud.google.com/apigee/docs/hybrid/supported-platforms.md.txt) for the ASM versions supported in hybrid version 1.7.

### Perform ASM setup and configuration steps


To complete the ASM installation, you must first follow ASM-specific setup and configuration
steps in the ASM documentation. Then, you must return here to complete the hybrid-specific
configuration before applying the configuration to the cluster.


The instructions to install and configure ASM are different depending on your platform. The
platforms are divided into the following categories:

- **GKE**: Google Kubernetes Engine clusters running on Google Cloud.
- **Outside Google Cloud** : Anthos clusters running on:
  - **Anthos clusters on VMware (GKE on-prem)**
  - **Anthos on bare metal**
  - **Anthos clusters on AWS**
  - **Amazon EKS**
- **Other Kubernetes Platforms** : Conformant clusters created and running on:
  - **AKS**
  - **EKS**
  - **OpenShift**

### GKE

### Prepare to install ASM

1. Check the environment variables you will need for the following steps, and set them if you you need to:

       echo $PROJECT_ID
       echo $CLUSTER_NAME
       echo $CLUSTER_LOCATION

2. Create an overlay file named `overlay.yaml` with the following contents:

   ```
   apiVersion: install.istio.io/v1alpha1
   kind: IstioOperator
   spec:
     components:
       ingressGateways:
         - name: istio-ingressgateway
           enabled: true
           k8s:
             nodeSelector:
               # default node selector, if different or not using node selectors, change accordingly.
               cloud.google.com/gke-nodepool: apigee-runtime
             resources:
               requests:
                 cpu: 1000m
             service:
               type: LoadBalancer
               loadBalancerIP: STATIC_IP # If you do not have a reserved static IP, leave this out.
               ports:
                 - name: http-status-port
                   port: 15021
                 - name: http2
                   port: 80
                   targetPort: 8080
                 - name: https
                   port: 443
                   targetPort: 8443
     meshConfig:
       accessLogFormat:
         '{"start_time":"%START_TIME%","remote_address":"%DOWNSTREAM_DIRECT_REMOTE_ADDRESS%","user_agent":"%REQ(USER-AGENT)%","host":"%REQ(:AUTHORITY)%","request":"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%","request_time":"%DURATION%","status":"%RESPONSE_CODE%","status_details":"%RESPONSE_CODE_DETAILS%","bytes_received":"%BYTES_RECEIVED%","bytes_sent":"%BYTES_SENT%","upstream_address":"%UPSTREAM_HOST%","upstream_response_flags":"%RESPONSE_FLAGS%","upstream_response_time":"%RESPONSE_DURATION%","upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%","upstream_cluster":"%UPSTREAM_CLUSTER%","x_forwarded_for":"%REQ(X-FORWARDED-FOR)%","request_method":"%REQ(:METHOD)%","request_path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%","request_protocol":"%PROTOCOL%","tls_protocol":"%DOWNSTREAM_TLS_VERSION%","request_id":"%REQ(X-REQUEST-ID)%","sni_host":"%REQUESTED_SERVER_NAME%","apigee_dynamic_data":"%DYNAMIC_METADATA(envoy.lua)%"}'
   ```
   - **`apigee-runtime`** is the default value for the node selector. This is the `apigee-runtime` node pool you created in [Step
     1: Create a cluster](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-create-cluster). If you are using a different node selector or are not using one, change or omit the `nodeSelector` property.
   - <var translate="no">STATIC_IP</var> is the IP address for your load balancer. If you have not set one, omit the `loadBalancerIP` property, but keep the `type` and `ports` properties.
3. Follow the instructions to prepare to install ASM:
   1. [Anthos
      prerequisites](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/anthos-service-mesh-prerequisites).
   2. [Permissions required to
      install Anthos Service Mesh](https://docs.cloud.google.com/service-mesh/v1.12/docs/installation-permissions).
   3. [Plan an installation](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/plan-install).
4. Install `asmcli` and any required tools like git, kubectl, and jq, following the instructions in [Install
   required tools](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/install-dependent-tools#install_required_tools).
5. Proceed through the step to [Grant
   cluster admin permissions](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/install-dependent-tools#grant_cluster_admin_permissions) and stop. Do not perform the "Validate project and cluster" step.

   > [!WARNING]
   > The `asmcli validate` command tries to validate the `istio-system` namespace, which in a fresh Apigee hybrid installation, you have not created yet. Therefore skip the "Validate project and cluster" step.

6. Install ASM with optional features. Specify the legacy ingress gateway with `--option legacy-default-ingressgateway`. for example:

   ```
   ./asmcli install \
     --verbose \
     --project_id $PROJECT_ID \
     --cluster_name $CLUSTER_NAME \
     --cluster_location $CLUSTER_LOCATION \
     --output_dir dir_path \
     --custom_overlay overlay.yaml \
     --enable_all \
     --option legacy-default-ingressgateway
   ```
   - <var translate="no">dir_path</var> is the output directory where you want `asmcli` to set up your the ASM installation, including all subdirectories.
   - <var translate="no">overlay.yaml</var> is the overlay file you created in the previous steps.


   Use these settings when following the instructions in
   [Install
   with optional features](https://cloud.google.com/service-mesh/v1.12/docs/unified-install/install-anthos-service-mesh#install_with_optional_features).

### Troubleshooting


If you encounter an error at refers to `gcloud container hub memberships register`,
you may have exceeded the maximum number of clusters registered with GKE Hub. For example:

```
asmcli_1.12: [WARNING]:  Command 'run_command gcloud
container hub memberships register my-hybrid-example
...' failed.
```


Try the following steps to remedy this error and then run `asmcli install` again:

1. List the GKE Hub memberships for your project:

   ```
   gcloud container hub memberships list --project=$PROJECT_ID
   ```
2. Delete the GKE Hub memberships:

   ```
   gcloud container hub memberships delete "membership" --project=$PROJECT_ID
   ```


For more information about GKE Hub limits, see
[Quotas and limits](https://docs.cloud.google.com/anthos/fleet-management/docs/quotas).

### Outside Google Cloud


These instructions are for installing and setting up ASM for Apigee hybrid instances using
Anthos to run on:

- **Anthos clusters on VMware (GKE on-prem)**
- **Anthos on bare metal**
- **Anthos clusters on AWS**
- **Amazon EKS**

### Prepare to install ASM

1. Check the environment variables you will need for the following steps, and set them if you you need to:

       echo ${PROJECT_ID}
       echo ${CLUSTER_NAME}
       echo ${CLUSTER_LOCATION}

2. Make note of the values you will need with `ASMCLI`. These are the values you will be asked to provide when following the steps in the ASM documentation:
   - <var translate="no">FLEET_PROJECT_ID</var> the name of the project your clusters will be associated with. Use the project you created for this install, stored in the `${PROJECT_ID}` environment variable.
   - <var translate="no">KUBECONFIG_FILE</var> The full path to the kubeconfig file. The default path is `$HOME/.kube/config`. for more information see [Organizing
     Cluster Access Using kubeconfig Files](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) in the Kubernetes documentation.
   - <var translate="no">DIR_PATH</var> the output directory for ASMCLI. This is the path where it will create the Istio configuration files. For example: `./asm`.
   - <var translate="no">GATEWAY_NAMESPACE</var> the namespace for your Istio ingress gateway, for example: `istio`.
   - <var translate="no">REVISION</var> the revision label for this release of ASM. Use `asm-1313-13`
   - <var translate="no">CONTEXT</var> the Kubernetes context. Check that kubernetes is using the context for you cluster with the following command:

     ```
     kubectl config get-contexts
     ```


     If your current cluster is not the current context, you can set it with the following
     command:

     ```
     kubectl config use-context CONTEXT
     ```
   - <var translate="no">USER_ACCOUNT</var> the account with cluster admin permissions you are using to manage the cluster.
3. Set the context to your project and region with the following commands:
   Set your default project ID:

   ```
   gcloud config set project ${PROJECT_ID}
   ```

   > [!NOTE]
   > **Note:** Do not set both the default region and zone. If you created your clusters with a region, set only the default region. If you created it with a zone, set only the default zone. In most cases, Apigee recommends working with regional clusters.


   If you are working with regional clusters, set your default compute region:

   ```
   gcloud config set compute/region ${CLUSTER_LOCATION}
   ```

   > [!NOTE]
   > **Note:** If you are working with zonal clusters, set your default compute zone *instead of* your default compute region:
   >
   > ```
   > gcloud config set compute/zone ${CLUSTER_LOCATION}
   > ```

4. Get credentials with the following command:

   ```
   gcloud container clusters get-credentials ${CLUSTER_NAME} --region ${CLUSTER_LOCATION} --project ${PROJECT_ID}
   ```

   > [!NOTE]
   > **Note:** If you are working with a zonal cluster, use the `--zone` flag instead of `--region`:
   >
   > ```
   > gcloud container clusters get-credentials ${CLUSTER_NAME} --zone ${CLUSTER_LOCATION} --project ${PROJECT_ID}
   > ```

5. Create an overlay file named `overlay.yaml` with the following contents:

   ```
   apiVersion: install.istio.io/v1alpha1
   kind: IstioOperator
   spec:
     components:
       ingressGateways:
         - name: istio-ingressgateway
           enabled: true
           k8s:
             nodeSelector:
               # default node selector, if different or not using node selectors, change accordingly.
               cloud.google.com/gke-nodepool: apigee-runtime
             resources:
               requests:
                 cpu: 1000m
             service:
               type: LoadBalancer
               loadBalancerIP: STATIC_IP # If you do not have a reserved static IP, leave this out.
               ports:
                 - name: http-status-port
                   port: 15021
                 - name: http2
                   port: 80
                   targetPort: 8080
                 - name: https
                   port: 443
                   targetPort: 8443
     meshConfig:
       accessLogFormat:
         '{"start_time":"%START_TIME%","remote_address":"%DOWNSTREAM_DIRECT_REMOTE_ADDRESS%","user_agent":"%REQ(USER-AGENT)%","host":"%REQ(:AUTHORITY)%","request":"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%","request_time":"%DURATION%","status":"%RESPONSE_CODE%","status_details":"%RESPONSE_CODE_DETAILS%","bytes_received":"%BYTES_RECEIVED%","bytes_sent":"%BYTES_SENT%","upstream_address":"%UPSTREAM_HOST%","upstream_response_flags":"%RESPONSE_FLAGS%","upstream_response_time":"%RESPONSE_DURATION%","upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%","upstream_cluster":"%UPSTREAM_CLUSTER%","x_forwarded_for":"%REQ(X-FORWARDED-FOR)%","request_method":"%REQ(:METHOD)%","request_path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%","request_protocol":"%PROTOCOL%","tls_protocol":"%DOWNSTREAM_TLS_VERSION%","request_id":"%REQ(X-REQUEST-ID)%","sni_host":"%REQUESTED_SERVER_NAME%","apigee_dynamic_data":"%DYNAMIC_METADATA(envoy.lua)%"}'
   ```
   - **`apigee-runtime`** is the default value for the node selector. This is the `apigee-runtime` node pool you created in [Step
     1: Create a cluster](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-create-cluster). If you are using a different node selector or are not using one, change or omit the `nodeSelector` property.
   - <var translate="no">STATIC_IP</var> is the IP address for your load balancer. If you have not set one, omit the `loadBalancerIP` property, but keep the `type` and `ports` properties.
6. Follow the instructions to prepare to install ASM:
   1. [Anthos
      prerequisites](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/anthos-service-mesh-prerequisites).
   2. [Permissions required to
      install Anthos Service Mesh](https://docs.cloud.google.com/service-mesh/v1.12/docs/installation-permissions).
   3. [Plan an installation](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/plan-install).
7. Install `asmcli` and any required tools like git, kubectl, and jq, following the instructions in [Install
   required tools](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/install-dependent-tools#install_required_tools).
8. Proceed through the step to [Grant
   cluster admin permissions](https://docs.cloud.google.com/service-mesh/v1.12/docs/unified-install/install-dependent-tools#grant_cluster_admin_permissions) and stop. Do not perform the "Validate project and cluster" step.

   > [!WARNING]
   > The `asmcli validate` command tries to validate the `istio-system` namespace, which in a fresh Apigee hybrid installation, you have not created yet. Therefore skip the "Validate project and cluster" step.

9. Install ASM with optional features. Specify the legacy ingress gateway with `--option legacy-default-ingressgateway`. for example:

   ```
   ./asmcli install \
     --verbose \
     --project_id $PROJECT_ID \
     --cluster_name $CLUSTER_NAME \
     --cluster_location $CLUSTER_LOCATION \
     --output_dir dir_path \
     --custom_overlay overlay.yaml \
     --enable_all \
     --option legacy-default-ingressgateway
   ```
   - <var translate="no">dir_path</var> is the output directory where you want `asmcli` to set up your the ASM installation, including all subdirectories.
   - <var translate="no">overlay.yaml</var> is the overlay file you created in the previous steps.


   Use these settings when following the instructions in
   [Install
   with optional features](https://cloud.google.com/service-mesh/v1.12/docs/unified-install/install-anthos-service-mesh#install_with_optional_features).

### Troubleshooting


If you encounter an error at refers to `gcloud container hub memberships register`,
you may have exceeded the maximum number of clusters registered with GKE Hub. For example:

```
asmcli_1.12: [WARNING]:  Command 'run_command gcloud
container hub memberships register my-hybrid-example
...' failed.
```


Try the following steps to remedy this error and then run `asmcli install` again:

1. List the GKE Hub memberships for your project:

   ```
   gcloud container hub memberships list --project=$PROJECT_ID
   ```
2. Delete the GKE Hub memberships:

   ```
   gcloud container hub memberships delete "membership" --project=$PROJECT_ID
   ```


For more information about GKE Hub limits, see
[Quotas and limits](https://docs.cloud.google.com/anthos/fleet-management/docs/quotas).

### Other Kubernetes platforms

### AKS

## Set up and download ASM

Read the following steps carefully before you begin.
We will ask you to perform some of the steps listed in the ASM documentation, then return here to
complete the installation.


This guide explains how to do a clean installation of Anthos Service Mesh (ASM) version
1.31.3-asm.13 on Anthos attached clusters. Use this guide to install Anthos Service Mesh
on the following environments:

- Amazon Elastic Kubernetes Service (Amazon EKS) on Kubernetes
- Microsoft Azure Kubernetes Service (Microsoft AKS) on Kubernetes
- Red Hat OpenShift

## Preparing to install Anthos Service Mesh

### Linux

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig
  ```

      openssl dgst -verify /dev/stdin -signature istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig istio-1.31.3-asm.13-linux-amd64.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Mac OS

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz.1.sig
  ```

      openssl dgst -sha256 -verify /dev/stdin -signature istio-1.31.3-asm.13-osx.tar.gz.1.sig istio-1.31.3-asm.13-osx.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-osx.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Windows

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip.1.sig
  ```

      openssl dgst -verify - -signature istio-1.31.3-asm.13-win.zip.1.sig istio-1.31.3-asm.13-win.zip <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-win.zip
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests\profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the \\bin directory to your PATH:

  ```
  set PATH=%CD%\bin:%PATH%
  ```

1. Now that ASM Istio is installed, check the version of `istioctl`:

   ```
   istioctl version
   ```
2. Create a namespace called istio-system for the control plane components:

   ```
   kubectl create namespace istio-system
   ```

### Installing Anthos Service Mesh

1. create a file called `overlay.yaml` with the following contents:

   ```
   apiVersion: install.istio.io/v1alpha1
   kind: IstioOperator
   spec:
     meshConfig:
       accessLogFile: /dev/stdout
       enableTracing: true
       accessLogFormat:
         '{"start_time":"%START_TIME%","remote_address":"%DOWNSTREAM_DIRECT_REMOTE_ADDRESS%","user_agent":"%REQ(USER-AGENT)%","host":"%REQ(:AUTHORITY)%","request":"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%","request_time":"%DURATION%","status":"%RESPONSE_CODE%","status_details":"%RESPONSE_CODE_DETAILS%","bytes_received":"%BYTES_RECEIVED%","bytes_sent":"%BYTES_SENT%","upstream_address":"%UPSTREAM_HOST%","upstream_response_flags":"%RESPONSE_FLAGS%","upstream_response_time":"%RESPONSE_DURATION%","upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%","upstream_cluster":"%UPSTREAM_CLUSTER%","x_forwarded_for":"%REQ(X-FORWARDED-FOR)%","request_method":"%REQ(:METHOD)%","request_path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%","request_protocol":"%PROTOCOL%","tls_protocol":"%DOWNSTREAM_TLS_VERSION%","request_id":"%REQ(X-REQUEST-ID)%","sni_host":"%REQUESTED_SERVER_NAME%","apigee_dynamic_data":"%DYNAMIC_METADATA(envoy.lua)%"}'
     components:
       ingressGateways:
       - name: istio-ingressgateway
         enabled: true
         k8s:
           service:
             type: LoadBalancer
             ports:
             - name: status-port
               port: 15021
               targetPort: 15021
             - name: http2
               port: 80
               targetPort: 8080
             - name: https
               port: 443
               targetPort: 8443
   ```
2. Install Anthos Service Mesh with `istioctl` using the `asm-multicloud` profile:

   ```
   istioctl install \
       --set profile=asm-multicloud \
       --set revision="asm-1313-13" \
       --filename overlay.yaml
   ```


   The `--set revision` argument adds a revision label in the format
   `istio.io/rev=asm-1313-13` to istiod. The revision label is used by the
   automatic sidecar injector webhook to associate injected sidecars with a particular istiod
   revision. To enable sidecar auto-injection for a namespace, you must label it with a revision
   that matches the label on istiod.

   > [!TIP]
   > **Tip:** The revision can only contain letters, numbers and dashes.

3. Check that the `istiod` pods are running with `kubectl get pods`:

   ```
   kubectl get pods -n istio-system
   ```

   Your output should look something like:

   ```
   NAME                                      READY   STATUS    RESTARTS   AGE
   istio-ingressgateway-88b6fd976-flgp2  1/1     Running   0          3m13s
   istio-ingressgateway-88b6fd976-p5dl9  1/1     Running   0          2m57s
   istiod-asm-1313-13-dbfb7c7b6-2ls88      1/1     Running   0          3m21s
   istiod-asm-1313-13-dbfb7c7b6-fnj8c      1/1     Running   1          3m21s
   ```
4. Verify that your install completed:

   ```
   kubectl get svc -n istio-system
   ```


   Your output should look something like:

   ```
   NAME                  TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                                                                      AGE
   istio-ingressgateway  LoadBalancer   172.200.48.52    34.74.177.168   15021:30479/TCP,80:30030/TCP,443:32200/TCP,15012:32297/TCP,15443:30244/TCP   3m35s
   istiod                ClusterIP      172.200.18.133   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        4m46s
   istiod-asm-1313-13     ClusterIP      172.200.63.220   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        3m43s
   ```

### EKS

## Set up and download ASM

Read the following steps carefully before you begin.
We will ask you to perform some of the steps listed in the ASM documentation, then return here to
complete the installation.


This guide explains how to do a clean installation of Anthos Service Mesh (ASM) version
1.31.3-asm.13 on Anthos attached clusters. Use this guide to install Anthos Service Mesh
on the following environments:

- Amazon Elastic Kubernetes Service (Amazon EKS) on Kubernetes
- Microsoft Azure Kubernetes Service (Microsoft AKS) on Kubernetes
- Red Hat OpenShift

## Preparing to install Anthos Service Mesh

### Linux

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig
  ```

      openssl dgst -verify /dev/stdin -signature istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig istio-1.31.3-asm.13-linux-amd64.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Mac OS

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz.1.sig
  ```

      openssl dgst -sha256 -verify /dev/stdin -signature istio-1.31.3-asm.13-osx.tar.gz.1.sig istio-1.31.3-asm.13-osx.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-osx.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Windows

- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip.1.sig
  ```

      openssl dgst -verify - -signature istio-1.31.3-asm.13-win.zip.1.sig istio-1.31.3-asm.13-win.zip <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-win.zip
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests\profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the \\bin directory to your PATH:

  ```
  set PATH=%CD%\bin:%PATH%
  ```

1. Now that ASM Istio is installed, check the version of `istioctl`:

   ```
   istioctl version
   ```
2. Create a namespace called istio-system for the control plane components:

   ```
   kubectl create namespace istio-system
   ```

### Installing Anthos Service Mesh

1. create a file called `overlay.yaml` with the following contents:

   ```
   apiVersion: install.istio.io/v1alpha1
   kind: IstioOperator
   spec:
     meshConfig:
       accessLogFile: /dev/stdout
       enableTracing: true
       accessLogFormat:
         '{"start_time":"%START_TIME%","remote_address":"%DOWNSTREAM_DIRECT_REMOTE_ADDRESS%","user_agent":"%REQ(USER-AGENT)%","host":"%REQ(:AUTHORITY)%","request":"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%","request_time":"%DURATION%","status":"%RESPONSE_CODE%","status_details":"%RESPONSE_CODE_DETAILS%","bytes_received":"%BYTES_RECEIVED%","bytes_sent":"%BYTES_SENT%","upstream_address":"%UPSTREAM_HOST%","upstream_response_flags":"%RESPONSE_FLAGS%","upstream_response_time":"%RESPONSE_DURATION%","upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%","upstream_cluster":"%UPSTREAM_CLUSTER%","x_forwarded_for":"%REQ(X-FORWARDED-FOR)%","request_method":"%REQ(:METHOD)%","request_path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%","request_protocol":"%PROTOCOL%","tls_protocol":"%DOWNSTREAM_TLS_VERSION%","request_id":"%REQ(X-REQUEST-ID)%","sni_host":"%REQUESTED_SERVER_NAME%","apigee_dynamic_data":"%DYNAMIC_METADATA(envoy.lua)%"}'
     components:
       ingressGateways:
       - name: istio-ingressgateway
         enabled: true
         k8s:
           service:
             type: LoadBalancer
             ports:
             - name: status-port
               port: 15021
               targetPort: 15021
             - name: http2
               port: 80
               targetPort: 8080
             - name: https
               port: 443
               targetPort: 8443
   ```
2. Install Anthos Service Mesh with `istioctl` using the `asm-multicloud` profile:

   ```
   istioctl install \
       --set profile=asm-multicloud \
       --set revision="asm-1313-13" \
       --filename overlay.yaml
   ```


   The `--set revision` argument adds a revision label in the format
   `istio.io/rev=asm-1313-13` to istiod. The revision label is used by the
   automatic sidecar injector webhook to associate injected sidecars with a particular istiod
   revision. To enable sidecar auto-injection for a namespace, you must label it with a revision
   that matches the label on istiod.

   > [!TIP]
   > **Tip:** The revision can only contain letters, numbers and dashes.

3. Check that the `istiod` pods are running with `kubectl get pods`:

   ```
   kubectl get pods -n istio-system
   ```

   Your output should look something like:

   ```
   NAME                                      READY   STATUS    RESTARTS   AGE
   istio-ingressgateway-88b6fd976-flgp2  1/1     Running   0          3m13s
   istio-ingressgateway-88b6fd976-p5dl9  1/1     Running   0          2m57s
   istiod-asm-1313-13-dbfb7c7b6-2ls88      1/1     Running   0          3m21s
   istiod-asm-1313-13-dbfb7c7b6-fnj8c      1/1     Running   1          3m21s
   ```
4. Verify that your install completed:

   ```
   kubectl get svc -n istio-system
   ```


   Your output should look something like:

   ```
   NAME                  TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                                                                      AGE
   istio-ingressgateway  LoadBalancer   172.200.48.52    34.74.177.168   15021:30479/TCP,80:30030/TCP,443:32200/TCP,15012:32297/TCP,15443:30244/TCP   3m35s
   istiod                ClusterIP      172.200.18.133   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        4m46s
   istiod-asm-1313-13     ClusterIP      172.200.63.220   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        3m43s
   ```

### OpenShift

## Set up and download ASM

Read the following steps carefully before you begin.
We will ask you to perform some of the steps listed in the ASM documentation, then return here to
complete the installation.


This guide explains how to do a clean installation of Anthos Service Mesh (ASM) version
1.31.3-asm.13 on Anthos attached clusters. Use this guide to install Anthos Service Mesh
on the following environments:

- Amazon Elastic Kubernetes Service (Amazon EKS) on Kubernetes
- Microsoft Azure Kubernetes Service (Microsoft AKS) on Kubernetes
- Red Hat OpenShift

## Preparing to install Anthos Service Mesh

### Linux

- Grant the `anyuid` security context constraint (SCC) to the istio-system with the following `oc` command:

  ```
  oc adm policy add-scc-to-group anyuid system:serviceaccounts:istio-system
  ```
- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig
  ```

      openssl dgst -verify /dev/stdin -signature istio-1.31.3-asm.13-linux-amd64.tar.gz.1.sig istio-1.31.3-asm.13-linux-amd64.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-linux-amd64.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Mac OS

- Grant the `anyuid` security context constraint (SCC) to the istio-system with the following `oc` command:

  ```
  oc adm policy add-scc-to-group anyuid system:serviceaccounts:istio-system
  ```
- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-osx.tar.gz.1.sig
  ```

      openssl dgst -sha256 -verify /dev/stdin -signature istio-1.31.3-asm.13-osx.tar.gz.1.sig istio-1.31.3-asm.13-osx.tar.gz <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-osx.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests/profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the /bin directory to your PATH:

  ```
  export PATH=$PWD/bin:$PATH
  ```

### Windows

- Grant the `anyuid` security context constraint (SCC) to the istio-system with the following OpenShift CLI (`oc`) command:

  ```
  oc adm policy add-scc-to-group anyuid system:serviceaccounts:istio-system
  ```
- Download the Anthos Service Mesh installation file to your current working directory:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip
  ```
- Download the signature file and use openssl to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/istio-1.31.3-asm.13-win.zip.1.sig
  ```

      openssl dgst -verify - -signature istio-1.31.3-asm.13-win.zip.1.sig istio-1.31.3-asm.13-win.zip <<'EOF'
      ---BEGIN PUBLIC KEY---
      MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEWZrGCUaJJr1H8a36sG4UUoXvlXvZ
      wQfk16sxprI2gOJ2vFFggdq3ixF2h4qNBt0kI7ciDhgpwS8t+/960IsIgw==
      ---END PUBLIC KEY---
      EOF

- Extract the contents of the file to any location on your file system. For example, to extract the contents to the current working directory:

  ```
  tar xzf istio-1.31.3-asm.13-win.zip
  ```


  The command creates an installation directory in your current working directory named
  `istio-1.31.3-asm.13` that contains:
  - Sample applications in the `samples` directory.
  - The `istioctl` command-line tool that you use to install Anthos Service Mesh is in the `bin` directory.
  - The Anthos Service Mesh configuration profiles are in the `manifests\profiles` directory.
- Ensure that you're in the Anthos Service Mesh installation's root directory:

  ```
  cd istio-1.31.3-asm.13
  ```
- For convenience, add the tools in the \\bin directory to your PATH:

  ```
  set PATH=%CD%\bin:%PATH%
  ```

1. Now that ASM Istio is installed, check the version of `istioctl`:

   ```
   istioctl version
   ```
2. Create a namespace called istio-system for the control plane components:

   ```
   kubectl create namespace istio-system
   ```

### Installing Anthos Service Mesh

1. create a file called `overlay.yaml` with the following contents:

   ```
   apiVersion: install.istio.io/v1alpha1
   kind: IstioOperator
   spec:
     meshConfig:
       accessLogFile: /dev/stdout
       enableTracing: true
       accessLogFormat:
         '{"start_time":"%START_TIME%","remote_address":"%DOWNSTREAM_DIRECT_REMOTE_ADDRESS%","user_agent":"%REQ(USER-AGENT)%","host":"%REQ(:AUTHORITY)%","request":"%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%","request_time":"%DURATION%","status":"%RESPONSE_CODE%","status_details":"%RESPONSE_CODE_DETAILS%","bytes_received":"%BYTES_RECEIVED%","bytes_sent":"%BYTES_SENT%","upstream_address":"%UPSTREAM_HOST%","upstream_response_flags":"%RESPONSE_FLAGS%","upstream_response_time":"%RESPONSE_DURATION%","upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%","upstream_cluster":"%UPSTREAM_CLUSTER%","x_forwarded_for":"%REQ(X-FORWARDED-FOR)%","request_method":"%REQ(:METHOD)%","request_path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%","request_protocol":"%PROTOCOL%","tls_protocol":"%DOWNSTREAM_TLS_VERSION%","request_id":"%REQ(X-REQUEST-ID)%","sni_host":"%REQUESTED_SERVER_NAME%","apigee_dynamic_data":"%DYNAMIC_METADATA(envoy.lua)%"}'
     components:
       ingressGateways:
       - name: istio-ingressgateway
         enabled: true
         k8s:
           service:
             type: LoadBalancer
             ports:
             - name: status-port
               port: 15021
               targetPort: 15021
             - name: http2
               port: 80
               targetPort: 8080
             - name: https
               port: 443
               targetPort: 8443
   ```
2. Install Anthos Service Mesh with `istioctl` using the `asm-multicloud` profile:

   ```
   istioctl install \
       --set profile=asm-multicloud \
       --set revision="asm-1313-13" \
       --filename overlay.yaml
   ```


   The `--set revision` argument adds a revision label in the format
   `istio.io/rev=asm-1313-13` to istiod. The revision label is used by the
   automatic sidecar injector webhook to associate injected sidecars with a particular istiod
   revision. To enable sidecar auto-injection for a namespace, you must label it with a revision
   that matches the label on istiod.

   > [!TIP]
   > **Tip:** The revision can only contain letters, numbers and dashes.

3. Check that the `istiod` pods are running with `kubectl get pods`:

   ```
   kubectl get pods -n istio-system
   ```

   Your output should look something like:

   ```
   NAME                                      READY   STATUS    RESTARTS   AGE
   istio-ingressgateway-88b6fd976-flgp2  1/1     Running   0          3m13s
   istio-ingressgateway-88b6fd976-p5dl9  1/1     Running   0          2m57s
   istiod-asm-1313-13-dbfb7c7b6-2ls88      1/1     Running   0          3m21s
   istiod-asm-1313-13-dbfb7c7b6-fnj8c      1/1     Running   1          3m21s
   ```
4. Verify that your install completed:

   ```
   kubectl get svc -n istio-system
   ```


   Your output should look something like:

   ```
   NAME                  TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                                                                      AGE
   istio-ingressgateway  LoadBalancer   172.200.48.52    34.74.177.168   15021:30479/TCP,80:30030/TCP,443:32200/TCP,15012:32297/TCP,15443:30244/TCP   3m35s
   istiod                ClusterIP      172.200.18.133   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        4m46s
   istiod-asm-1313-13     ClusterIP      172.200.63.220   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        3m43s
   ```

## Customizing the ASM installation


The ASM installation you just performed is a minimal installation, sufficient to test and use
Apigee hybrid for basic use cases. For information on addressing more advanced use cases, such as
adding, removing, or modifying load balancer port numbers, see
[Enabling optional
features](https://docs.cloud.google.com/service-mesh/v1.9/docs/enable-optional-features).

## Summary


You now have cert-manager and ASM installed, and you are ready to install the
Apigee hybrid command line tool on your local machine.
[1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-create-cluster.md.txt) [2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-cert-manager.md.txt) [3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-asm.md.txt) [(NEXT) Step 4: Install apigeectl](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-apigeectl.md.txt) [5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-service-accounts.md.txt) [6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-create-tls-certificates.md.txt) [7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-configure-cluster.md.txt) [8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-enable-synchronizer-access.md.txt) [9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.7/install-hybrid-runtime.md.txt)

<br />