[[["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-08-26 UTC."],[[["\u003cp\u003eApigee hybrid version 1.2 is end-of-life and should be upgraded to a newer version, as detailed in the supported versions documentation.\u003c/p\u003e\n"],["\u003cp\u003eApigee hybrid runtime can be installed on Google Kubernetes Engine (GKE), Anthos (GKE on-prem), and Azure Kubernetes Service (AKS) using the specified versions.\u003c/p\u003e\n"],["\u003cp\u003eBefore beginning the runtime installation, you must complete the GCP and UI setup and obtain an authorized TLS key/certificate pair.\u003c/p\u003e\n"],["\u003cp\u003eYou can install Apigee hybrid in a shared cluster with other workloads or in a separate cluster, each with its own considerations for management and maintenance.\u003c/p\u003e\n"],["\u003cp\u003eThe runtime quickstart process involves creating a cluster, installing apigeectl, configuring the cluster with an overrides file, and installing the hybrid runtime, with specific guides available for GKE, GKE on-prem, and AKS.\u003c/p\u003e\n"]]],[],null,["# Part 2: Runtime quickstart\n\n| You are currently viewing version 1.2 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nSupported platforms\n-------------------\n\n| **UPGRADING:** If you are upgrading from v1.1.x to v1.2.0, see [Upgrading Apigee hybrid](/apigee/docs/hybrid/v1.2/upgrade) for instructions. If you are performing a new installation, continue with the configurations described below.\n\n\nYou can install hybrid runtime on the following platforms:\n\n| Do not enable GCP [Virtual Private Cloud (VPC) Service Controls](https://cloud.google.com/vpc-service-controls) with Apigee hybrid. You cannot use Apigee hybrid when VPC Service Controls are enabled.\n\nPrerequisites\n-------------\n\nThis section describes tasks you must accomplish before you begin the runtime plane quickstart\ninstall.\n\n| **Note about clusters:** You can create a new separate cluster for Apigee hybrid or you can install it in a cluster that is running other workloads. \n|\n| - **Shared cluster:** If you install Apigee hybrid in a cluster running other workloads, you need to Upgrade and maintain your GKE/AKS cluster at the versions and features required in common for Apigee hybrid and for your other workloads. You may want to develop a plan to migrate one or more workloads in case conflicts arise between supported versions and requirements.\n| - **Separate cluster:** Creating a dedicated cluster Apigee hybrid adds isolation. It also adds the operational effort of maintaining the new cluster.\n| Both options are valid.\n\nAfter you have satisfied the above prerequisites, you can continue with the steps in\n[the next section](#steps).\n\nProcess overview\n----------------\n\nThe general process for performing the runtime quickstart is as follows:\n\n1. Create a cluster and set up your shell environment.\n2. Install apigeectl, plus set up your hybrid project directories, create service accounts, and create TLS certs.\n3. Configure the cluster by creating and then applying the settings in an overrides file.\n4. Install hybrid runtime, enable Synchronizer access, and expose the MART endpoint to your hybrid organization.\n\nTo get started, go to the quickstart for your platform:"]]
