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. - 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 | grep \*
- 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
Note: Apigee hybrid 1.6 supports kubectl
version 1.21 and newer. If you are installing an older version of hybrid and usingkubectl
version 1.7 or older the syntax for the--dry-run
flag will be--dry-run=true
. You will need to update yourkubectl
to version 1.21 or newer before installing Apigee hybrid 1.6. - 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 istio-system
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.