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, seeSupported versions.

Supported platforms

UPGRADING:If you are upgrading from v1.1.x tov1.2.0, seeUpgrading Apigee hybrid for instructions. If you are performinga new installation, continue with the configurations described below.

You can install hybrid runtime on the following platforms:

Platform	Version
Google Kubernetes Engine (GKE)	Version 1.14.x and 1.15.x
Anthos (GKE on-prem)	Version 1.2.x and 1.3.x
Azure Kubernetes Service (AKS)	1.14.x

Do not enable GCP Virtual Private Cloud (VPC) Service Controls with Apigee hybrid. You cannot use Apigee hybrid when VPC Service Controls are enabled.

Prerequisites

This section describes tasks you must accomplish before you begin the runtime plane quickstartinstall.

To ensure that you can successfully begin the runtime installation (as described in this section):
Complete the GCP and UI setup steps in Configure GCP services and hybrid UI.
Obtain an authorized TLS key/certificate pair (required by the MART ingress gateway). The credentials must be issued by a trusted certificate authority (CA). For an example using the open source Let's Encrypt CA, seeObtain TLS credentials: An example.

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.

• 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.
• Separate cluster: Creating a dedicated cluster Apigee hybrid adds isolation. It also adds the operational effort of maintaining the new cluster.

Both options are valid.

After you have satisfied the above prerequisites, you can continue with the steps inthe next section.

Process overview

The general process for performing the runtime quickstart is as follows:

1. Create a cluster and set up your shell environment.
2. Install apigeectl, plus set up your hybrid project directories, create service accounts, and create TLS certs.
3. Configure the cluster by creating and then applying the settings in an overrides file.
4. Install hybrid runtime, enable Synchronizer access, and expose the MART endpoint to your hybrid organization.

To get started, go to the quickstart for your platform:

GKE Quickstart

GKE on-prem Quickstart

AKS Quickstart