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-filesdirectory.cd $HYBRID_FILES
- Verify that
kubectlis 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
KUBECONFIGvariable 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
initcommand with the--dry-runflag as follows:${APIGEECTL_HOME}/apigeectl init -f overrides/overrides.yaml --dry-run=clientNote: Apigee hybrid 1.8 supports kubectlversion 1.21 and newer. If you are installing an older version of hybrid and usingkubectlversion 1.8 or older the syntax for the--dry-runflag will be--dry-run=true. You will need to update yourkubectlto version 1.21 or newer before installing Apigee hybrid 1.8. - If there are no errors, execute the
initcommand as follows:${APIGEECTL_HOME}/apigeectl init -f overrides/overrides.yamlThe
initcommand 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.yamlkubectl 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
applycommand with the--dry-runflag.${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.yamlRepeat this step until the pods are all ready. The pods may take several minutes to start up.