This section describes the basic requirements for setting up a
Google Kubernetes Engine (GKE) cluster
suitable for an Apigee hybrid production installation.
Creating the cluster
For information about creating GKE clusters, see
Creating a cluster in the GKE documentation.
Production cluster requirements
Follow these requirements when creating your production cluster:
Software versions
Requirement
Value
Kubernetes version
Version 1.13 or later
You can find the supported Kubernetes cluster versions by issuing the following
command:
gcloud container get-server-config
Supported versions are returned under the validMasterVersions: heading.
Choose these template configuration options for your production GKE cluster:
Configuration
Value
Cluster template
Standard cluster
Location type
Regional (recommended)
Availability zones
3
Autoscaling
Enable autoscaling for your nodes, with the minimum and
maximum number of instances set to the same number. GKE will give
you a warning about setting the values to the same number. You can
ignore this warning.
Storage is provisioned dynamically using the StatefulSet dynamic provisioner.
Node requirements
A
node pool is a group of nodes within a cluster that all have the same configuration. By
default, you must configure two node pools in your cluster -- one for the stateful Cassandra
pods and one for the rest of the pods, which are stateless.
Configure these two node pools
as described below:
Stateful node pool configuration
Configure a stateful node pool as follows:
Configuration
Value
Name
apigee-data
Minimum number of nodes
3
Machine type
N1-standard-8 (Standard machine type with 8 vCPUs, 30 GB of memory)
Storage
Storage will be provisioned dynamically using StatefulSet
dynamic provisioner
Stateless node pool configuration
Configure a stateless node pool as follows:
Configuration
Value
Name
apigee-runtime
Minimum number of nodes
3 (1 per zone)
Machine type
N1-standard-4 (Standard machine type with 4 vCPUs, 15 GB of memory)
[[["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-25 UTC."],[[["\u003cp\u003eThe Apigee hybrid documentation version 1.1 is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eSetting up a production Google Kubernetes Engine (GKE) cluster for Apigee hybrid requires a cluster with Kubernetes version 1.13 or later and kubectl version 1.13.x or later.\u003c/p\u003e\n"],["\u003cp\u003eA production cluster should be a regional standard cluster with 3 availability zones, enabled autoscaling, and storage provisioned dynamically via StatefulSet.\u003c/p\u003e\n"],["\u003cp\u003eTwo node pools are required: a stateful node pool named \u003ccode\u003eapigee-data\u003c/code\u003e with a minimum of 3 nodes, and a stateless node pool named \u003ccode\u003eapigee-runtime\u003c/code\u003e also with a minimum of 3 nodes, one per zone.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eapigee-data\u003c/code\u003e node pool should use the N1-standard-8 machine type, while the \u003ccode\u003eapigee-runtime\u003c/code\u003e node pool should use the N1-standard-4 machine type.\u003c/p\u003e\n"]]],[],null,[]]
