> [!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/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)


Starting with Apigee hybrid version 1.8, Apigee hybrid uses Apigee ingress gateway to provide an
ingress gateway for your hybrid installation. If you prefer to use Anthos Service Mesh for
ingress, follow these steps to install Anthos Service Mesh in your cluster.


## Supported Anthos Service Mesh versions


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


If you are upgrading your hybrid installation, follow the instructions in
[Upgrade Anthos Service Mesh](https://docs.cloud.google.com/apigee/docs/hybrid/v1.8/upgrade.md.txt#upgrade-Anthos%20Service%20Mesh).

## Install Anthos Service Mesh


Perform these steps on a fresh Apigee hybrid installation only if you are not using Apigee ingress gateway.

Perform the procedures using the Anthos Service Mesh documentation appropriate for your platform:


The instructions to install and configure Anthos Service Mesh 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


The sequence for installing Anthos Service Mesh is as follows:

1. Prepare for the installation.
2. Install the new version of Anthos Service Mesh.

### Prepare to install Anthos Service Mesh

1. Review the requirements in [Upgrade Anthos
   Service Mesh](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/upgrade), but do not perform the upgrade yet.
2. Create a new `overlay.yaml` file or verify that your existing `overlay.yaml` contains 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)%"}'
   ```
3. Follow the instructions in the following sections in the Anthos Service Mesh documentation:

   > [!NOTE]
   > **Important:** Make sure to follow the instructions to upgrade Anthos Service Mesh with optional features, and to include your `overlay.yaml`.

   1. [Download
      asmcli](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#download_asmcli)
   2. [Grant
      cluster admin permissions](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#grant_cluster_admin_permissions)
   3. [Validate
      project and cluster](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#validate_project_and_cluster)
   4. [Upgrade
      with optional features](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/upgrade#upgrade_with_optional_features). Stop before starting the "Upgrade Gateways section".

### Outside Google Cloud


These instructions cover upgrading Anthos Service Mesh on:

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


The sequence for installing Anthos Service Mesh is as follows:

1. Prepare for the installation.
2. Install the new version of Anthos Service Mesh.

### Prepare to install Anthos Service Mesh

1. Review the requirements in [Upgrade Anthos
   Service Mesh](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/upgrade), but do not perform the upgrade yet.
2. Create a new `overlay.yaml` file or verify that your existing `overlay.yaml` contains 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
     values:
       gateways:
         istio-ingressgateway:
           runAsRoot: true

     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)%"}'
   ```
3. Follow the instructions in the following sections in the Anthos Service Mesh documentation:

   > [!NOTE]
   > **Important:** Make sure to follow the instructions to upgrade Anthos Service Mesh with optional features, and to include your `overlay.yaml`.

   1. [Download
      asmcli](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#download_asmcli)
   2. [Grant
      cluster admin permissions](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#grant_cluster_admin_permissions)
   3. [Validate
      project and cluster](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/install-dependent-tools#validate_project_and_cluster)
   4. [Upgrade
      with optional features](https://docs.cloud.google.com/service-mesh/v1.15/docs/unified-install/upgrade#upgrade_with_optional_features). Stop before starting the "Upgrade Gateways section".

### AKS / EKS

### 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/1.17.8-asm.4-distroless-linux-amd64.tar.gz
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-linux-amd64.tar.gz.1.sig
  ```

      openssl dgst -verify /dev/stdin -signature 1.17.8-asm.4-distroless-linux-amd64.tar.gz.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-linux-amd64.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- 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/1.17.8-asm.4-distroless-osx.tar.gz
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-osx.tar.gz.1.sig
  ```

      openssl dgst -sha256 -verify /dev/stdin -signature 1.17.8-asm.4-distroless-osx.tar.gz.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-osx.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- 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/1.17.8-asm.4-distroless-win.zip
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-win.zip.1.sig
  ```

      openssl dgst -verify - -signature 1.17.8-asm.4-distroless-win.zip.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-win.zip
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- For convenience, add the tools in the \\bin directory to your PATH:

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

1. Now that Anthos Service Mesh 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. Edit your `overlay.yaml` file or create a new one 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-1178-1" \
       --filename overlay.yaml
   ```


   Your output should look something like:

   ```
   kubectl get pods -n istio-system
   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-1178-1-798ffb964-2ls88       1/1     Running   0          3m21s
   istiod-asm-1178-1-798ffb964-fnj8c       1/1     Running   1          3m21s
   ```


   The `--set revision` argument adds a revision label in the format
   `istio.io/rev=asm-1178-1` 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`.
3. 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-1178-1       ClusterIP      172.200.63.220   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        3m43s
   ```

### OpenShift

### Preparing to install Anthos Service Mesh

1. Before installing the new version, determine the current revision. You will need this information to delete the *validating webhook* and *mutating webhook* from your current Anthos Service Mesh installation. Use the following command to store the current `istiod` revision to an environment variable:

       export DELETE_REV=$(kubectl get deploy -n istio-system -l app=istiod -o jsonpath={.items[*].metadata.labels.'istio\.io\/rev'}'{"\n"}')
       echo $DELETE_REV


   Your output should look something like `1.16`

   > [!NOTE]
   > **Note:** If the command returns multiple values, set the value of `DELETE_REV` to the oldest version and follow the procedure to delete the oldest version, then repeat the process until you have deleted all versions.

### Linux

- 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/1.17.8-asm.4-distroless-linux-amd64.tar.gz
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-linux-amd64.tar.gz.1.sig
  ```

      openssl dgst -verify /dev/stdin -signature 1.17.8-asm.4-distroless-linux-amd64.tar.gz.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-linux-amd64.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- 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 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/1.17.8-asm.4-distroless-osx.tar.gz
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-osx.tar.gz.1.sig
  ```

      openssl dgst -sha256 -verify /dev/stdin -signature 1.17.8-asm.4-distroless-osx.tar.gz.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-osx.tar.gz
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- 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/1.17.8-asm.4-distroless-win.zip
  ```
- Download the signature file and use OpenSSL to verify the signature:

  ```
  curl -LO https://storage.googleapis.com/gke-release/asm/1.17.8-asm.4-distroless-win.zip.1.sig
  ```

      openssl dgst -verify - -signature 1.17.8-asm.4-distroless-win.zip.1.sig 1.17.8-asm.4-distroless.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 1.17.8-asm.4-distroless-win.zip
  ```


  The command creates an installation directory in your current working directory named
  `1.17.8-asm.4-distroless` 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 1.17.8-asm.4-distroless
  ```
- For convenience, add the tools in the \\bin directory to your PATH:

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

2. Now that Anthos Service Mesh Istio is installed, check the version of `istioctl`:

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

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

### Configure the validating webhook


When you install Anthos Service Mesh, you set a revision label on `istiod`. You need to set the same
revision on the validating webhook.

1. Create a file called `istiod-service.yaml` with the following contents:

   ```
   apiVersion: v1
   kind: Service
   metadata:
     name: istiod
     namespace: istio-system
     labels:
       istio.io/rev: asm-1178-1
       app: istiod
       istio: pilot
       release: istio
   spec:
     ports:
       - port: 15010
         name: grpc-xds # plaintext
         protocol: TCP
       - port: 15012
         name: https-dns # mTLS with k8s-signed cert
         protocol: TCP
       - port: 443
         name: https-webhook # validation and injection
         targetPort: 15017
         protocol: TCP
       - port: 15014
         name: http-monitoring # prometheus stats
         protocol: TCP
     selector:
       app: istiod
       istio.io/rev: asm-1178-1
     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)%"}'
   ```
2. Use `kubectl` to apply the validating webhook configuration:

   ```
   kubectl apply -f istiod-service.yaml
   ```
3. Verify that the configuration was applied:

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


   The response should look similar to:

   ```
   NAME     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                                 AGE
   istiod   ClusterIP   172.200.18.133   <none>        15010/TCP,15012/TCP,443/TCP,15014/TCP   22s
   ```

### Installing Anthos Service Mesh

1. Edit your `overlay.yaml` file or create a new one 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-1178-1" \
       --filename overlayfile.yaml
   ```


   Your output should look something like:

   ```
   kubectl get pods -n istio-system
   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-1178-1-798ffb964-2ls88       1/1     Running   0          3m21s
   istiod-asm-1178-1-798ffb964-fnj8c       1/1     Running   1          3m21s
   ```


   The `--set revision` argument adds a revision label in the format
   `istio.io/rev=1.6.11-asm.1` 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`.
3. 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-1178-1       ClusterIP      172.200.63.220   <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP                                        3m43s
   ```