GKE non-production cluster requirements

You are currently viewing version 1.1 of the Apigee hybrid documentation. This version is end of life. You should upgrade to a newer version. For more information, see Supported versions.

Version 1.1 (unsupported)

   Supported versions:

• v1.13 (latest)                        
• v1.12                         
• v1.11                         
• List of supported versions

   Unsupported versions:

• v1.10                                      
• v1.9                                         
• v1.8                                         
• v1.7                                         
• v1.6                                         
• v1.5                                         
• v1.4                                         
• v1.3                                         
• v1.2                                         
• v1.1                                         

This section describes the basic requirements for setting up a Google Kubernetes Engine (GKE) cluster suitable for an Apigee hybrid non-production installation.

A non-production configuration typically includes fewer nodes, consumes fewer resources, and runs in fewer zones or regions than a production cluster. Non-production clusters are commonly used for demonstration and development purposes.

Creating the cluster

For information about creating GKE clusters, see Creating a cluster in the GKE documentation.

Non-production cluster requirements

Follow these requirements when creating your non-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.
kubectl version	Version 1.13.x or later. See Install and Set Up kubectl.

Cluster template configuration

Choose these template configuration options for your non-production GKE cluster:

Configuration	Value
Cluster template	Standard cluster
Location type	Zonal
Availability zones	3
Storage	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 NOTE: You must use the name apigee-data. If you want to use another node pool name, see Configure dedicated node pools.
Minimum number of nodes	3
Machine type	N1-standard-4 (Standard machine type with 4 vCPUs, 15 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 NOTE: You must use the name apigee-runtime. If you want to use another node pool name, see Configure dedicated node pools.
Minimum number of nodes	3 (If you run into resource constraints, choose 2)
Machine type	N1-standard-4 (Standard machine type with 4 vCPUs, 15 GB of memory)