Step 9: Install hybrid runtime

Apply the configuration to the cluster

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

Be sure that you are in the hybrid-base-directory/hybrid-files directory.
```
cd $HYBRID_FILES
```
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.
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
```
For Anthos on bare metal, AWS on GKE, EKS, and GKE on prem platforms only, Verify that the KUBECONFIG variable is set using the following command:
```
echo ${KUBECONFIG}
```
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
```
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 Apigee Deployment Controller and Apigee Admission Webhook.

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.

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

If there are no errors, you can apply the Apigee-specific runtime components to the cluster with the following command:
```
${APIGEECTL_HOME}/apigeectl apply -f overrides/overrides.yaml
```
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.

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 2 3 4 5 6 7 8 9 (NEXT) Step 10: Set up Workload Identity

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 2