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
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:
Note: Apigee hybrid 1.8 supports kubectl
version 1.21 and newer. If you are installing an older version of hybrid
and using kubectl version 1.8 or older the syntax for the
--dry-run flag will be --dry-run=true. You will
need to update your kubectl to version 1.21 or newer before
installing Apigee hybrid 1.8.
If there are no errors, execute the init command as follows:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-07 UTC."],[[["This documentation refers to Apigee hybrid version 1.8, which is now end-of-life and requires an upgrade to a newer version."],["Installing Apigee hybrid involves navigating to the `\u003cvar translate=\"no\"\u003ehybrid-base-directory\u003c/var\u003e` `/hybrid-files` directory and executing commands from there, as the overrides file uses relative paths."],["Before applying changes, users should perform dry runs of the `init` and `apply` commands to identify potential errors without altering the cluster."],["The installation process uses `apigeectl` commands to initialize and apply configurations, followed by checking pod readiness with `kubectl` commands."],["After successfully applying configurations, Apigee-specific runtime components are installed, and the user is prompted to expose Apigee ingress as the next step."]]],[]]
