> [!CAUTION]
> You are currently viewing version 1.11 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.11 </button>

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

## 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.

   ```
   cd $HYBRID_FILES
   ```

   > [!NOTE]
   > **Note:** Because the overrides file specifies service account files using paths relative to your `hybrid-base-directory/hybrid-files` directory, you must execute the commands from within that 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 current-context
   ```

   The result should include the name of the cluster you are deploying Apigee hybrid in. For
   example, on GKE, the context name is usually in the form
   `gke_project-id_cluster-location_cluster-name`, as
   in:

   ```
   gke_my-project_us-central1_my-cluster
   ```

   If the name cluster name in the context does not match, the following command will get the
   `gcloud` credentials of the cluster and set the `kubectl` context:

   ### Regional clusters

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

   ### Zonal clusters

   ```
   gcloud container clusters get-credentials $CLUSTER_NAME \
   --zone $CLUSTER_LOCATION \
   --project $PROJECT_ID
   ```
3. *For **Anthos on bare metal** , **AWS on GKE** , **EKS** , and **GKE on prem** platforms only*, Verify that the [`KUBECONFIG`](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable) variable is set using the following command:

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

   ```
   ${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.11/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 apigee
   ```


   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.

   ```
   ${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.11/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.

**Important:** Follow the steps in the [1.11.2-hotfix.3. release notes](https://docs.cloud.google.com/apigee/docs/hybrid/release-notes.md.txt#hybrid_1112-hotfix.3) to make sure you have installed the latest version of the hybrid runtime.

> [!NOTE]
> **Congratulations!**
>
> You've successfully installed and configured the Apigee hybrid runtime plane.

## GKE with Workload Identity

If you are installing Apigee hybrid on GKE and you are configuring Workload Identity to authenticate service accounts, in the next
step, you will configure the associations between the Kubernetes service accounts and the Google service accounts for your cluster.
[1](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-create-cluster.md.txt) [2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-cert-manager.md.txt) [3](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-apigeectl.md.txt) [4](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-service-accounts.md.txt) [5](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-create-tls-certificates.md.txt) [6](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-configure-cluster.md.txt) [7](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-enable-synchronizer-access.md.txt) [8](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-check-cluster.md.txt) [9](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-hybrid-runtime.md.txt) [(NEXT) Step 10: Set up Workload Identity](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-workload-identity.md.txt)

<br />

## All other installations

In the next step, you will configure the Apigee ingress gateway and deploy a proxy to test your installation.
[(NEXT) Step 1: Expose Apigee ingress](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-expose-apigee-ingress.md.txt) [2](https://docs.cloud.google.com/apigee/docs/hybrid/v1.11/install-deploy-proxy.md.txt)

<br />