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

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

## Enable synchronizer access


To enable synchronizer access:

1. Create a Google Cloud service account and add the **Apigee Organization Admin** role to it. This service account will be used to authenticate an API call that you will make in a later step. An easy way to create the service account is through the GCP console. For instructions, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#iam-service-accounts-create-gcloud) in the GCP documentation.


   For example, the following `gcloud` commands will create the service account and
   assign the **Apigee Organization Admin** to it:
   1. Create the account:

      ```
      gcloud iam service-accounts create apigee-org-admin \
          --display-name="apigee-org-admin"
      ```


      Where <var translate="no">apigee-org-admin</var> is the name of the service account you are creating.
      "`apigee-org-admin`" is recommended for this tutorial.
   2. Assign the **Apigee Org Admin** role to the service account:

      ```
      gcloud projects add-iam-policy-binding $PROJECT_ID \
          --member="serviceAccount:apigee-org-admin@$PROJECT_ID.iam.gserviceaccount.com" \
          --role="roles/apigee.admin"
      ```


      Where:
      - <var translate="no">$PROJECT_ID</var> is the name of your Google Cloud project that you created in [Step 2: Create a Google Cloud project](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/precog-gcpproject.md.txt).
      - <var translate="no">apigee-org-admin</var> is the name of the service account you just created.
      - **roles/apigee.admin** is the **Apigee Org Admin** role.
2. Download the service account key to your system. Use the following command to make download the key into your `service-accounts/` directory. For more information see the instructions in [Creating service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#iam-service-account-keys-create-gcloud) in the GCP documentation.
   1. Make sure you are in the `/hybrid-base-directory/hybrid-files/` directory.
   2. Download the key:

      ```
      gcloud iam service-accounts keys create ./service-accounts/$PROJECT_ID-apigee-org-admin.json \
        --iam-account apigee-org-admin@$PROJECT_ID.iam.gserviceaccount.com
      ```


      The output should look something like:

      ```
      created key [a0b1c2d3e4f5a0b1c2d3e4f5a0b1c2d3e4f5a0b1] of type [json] as [./service-accounts/hybrid-
      example-apigee-org-admin.json] for [apigee-org-admin@my-hybrid.iam.gserviceaccount.com]
      $ 
      ```
3. Verify the path to the Apigee Org Admin service account key with the following command:

   ```
   ls service-accounts/*admin*
   ```

   The result should look something like the following:

   ```
   service-accounts/hybrid-example-apigee-org-admin.json
   ```
4. Create an **ORG_ADMIN_ACCOUNT** environment variable with the name of the key file. For example:

   ```
   export ORG_ADMIN_ACCOUNT="hybrid-example-apigee-org-admin.json"
   ```
5. Execute the following commands to get a token:

       export GOOGLE_APPLICATION_CREDENTIALS=./service-accounts/$ORG_ADMIN_ACCOUNT
       export TOKEN=$(gcloud auth application-default print-access-token)

6. Get the email address for your `apigee-synchronizer` service account with the following command:

   ```
   gcloud iam service-accounts list --filter "apigee-synchronizer"
   ```


   If it matches the pattern `apigee-synchronizer$ORG_NAME.iam.gserviceaccount.com`, you
   can use that pattern in the next step.
7. Call the [setSyncAuthorization](https://docs.cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations/setSyncAuthorization.md.txt) API to enable the required permissions for Synchronizer using the following command:

   ```
   curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type:application/json" \
     "https://apigee.googleapis.com/v1/organizations/$ORG_NAME:setSyncAuthorization" \
      -d '{"identities":["'"serviceAccount:apigee-synchronizer@$ORG_NAME.iam.gserviceaccount.com"'"]}'
   ```


   Where:
   - **`$ORG_NAME`**: The name of your hybrid organization.
   - **`apigee-synchronizer$ORG_NAME.iam.gserviceaccount.com`**: The email address of the apigee-syncnronizer service account.
8. To verify that the service account was set, use the following command to call the API to get a list of service accounts:

   ```
   curl -X POST -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type:application/json" \
     "https://apigee.googleapis.com/v1/organizations/$ORG_NAME:getSyncAuthorization" \
      -d ''
   ```


   The output looks similar to the following:

   ```
   {
      "identities":[
         "serviceAccount:my-synchronizer-manager-service_account@my_project_id.iam.gserviceaccount.com"
      ],
      "etag":"BwWJgyS8I4w="
   }
   ```

## Apply the configuration to the cluster


Use the following steps to install Apigee hybrid into your cluster:

1. Be sure that you are in the `hybrid-base-directory/hybrid-files` directory.
2. Verify that `kubectl` is set to the correct context using the following command. The current context should be set to the cluster to which you are deploying Apigee hybrid.

   ```
   kubectl config get-contexts
   ```
3. *For **AWS on GKE** , **EKS** , and **GKE on prem** platforms only*, Verify that the `KUBECONFIG` variable is set using the following command.

   ```
   echo $KUBECONFIG
   ```
4. Do a *dry run* initialization. Execute the `init` command with the `--dry-run` flag. Doing a dry run lets you check for any errors before any changes are made to the cluster.


   In hybrid version 1.4.4, the syntax of the `--dry-run`
   flag depends on the version of `kubectl` you are running. Check the version of
   `kubectl` with the following command:

   ```
   kubectl version
   ```


   `kubectl` version 1.17 and older:

   ```
   $APIGEECTL_HOME/apigeectl init -f overrides/overrides.yaml --dry-run=true
   ```


   `kubectl` version 1.18 and newer:

   ```
   $APIGEECTL_HOME/apigeectl init -f overrides/overrides.yaml --dry-run=client
   ```
5. If there are no errors, execute the `init` command as follows:

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

   The `init` command installs the [Apigee deployment
   services](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/apigee-deployment-services) Apigee Deployment Controller and Apigee Admission Webhook.
6. To check the status of the deployment, you can use the following commands:

       $APIGEECTL_HOME/apigeectl check-ready -f overrides/overrides.yaml
       kubectl get pods -n apigee-system
       kubectl get pods -n istio-system


   When the pods are ready, go to the next step.
7. Do a *dry run* install. Execute the `apply` command with the `--dry-run` flag.


   `kubectl` version 1.17 and older:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides/overrides.yaml --dry-run=true
   ```


   `kubectl` version 1.18 and newer:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides/overrides.yaml --dry-run=client
   ```
8. If there are no errors, you can apply the [Apigee-specific runtime components](https://docs.cloud.google.com/apigee/docs/hybrid/v1.4/what-is-hybrid.md.txt#about-the-runtime-plane) to the cluster with the following command:

   ```
   $APIGEECTL_HOME/apigeectl apply -f overrides/overrides.yaml
   ```
9. To check the status of the deployment, run the following command:

   ```
   $APIGEECTL_HOME/apigeectl check-ready -f overrides/overrides.yaml
   ```


   Repeat this step until the pods are all ready. The pods may take several minutes to start up.

> [!NOTE]
> **Congratulations!**
>
> You've successfully installed Apigee hybrid. You are now ready to test
> it.