Scale and autoscale runtime services

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.

Version 1.2 (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                                         

You can scale most services running in Kubernetes from the command line or in a configuration override. You can set scaling parameters for Apigee hybrid runtime services in the overrides.yaml file.

How you scale and autoscale each service depends on the type of service.

TIP: You can use the -w option to continuously watch your nodes, as the following example shows:

kubectl get nodes -w ...

For more information on scaling, see the Kubernetes documentation.

The following table summarizes the hybrid runtime services and how you can scale and autoscale them in configurations or from the command line:

Service	Implemented As	Scaling
Cassandra	StatefulSet	(Scale up only) To scale up on the command line, you can use the kubectl scale or patch options. To scale up via configuration, set the value of the cassandra object's replicaCount configuration property in the overrides.yaml file. NOTE: The default replication factor for all keyspaces is three. As a result, Apigee recommends that you scale the replicas by a factor of three. For more information on setting configuration properties, see Manage runtime plane components. StatefulSets do not support autoscaling. Cassandra is deployed in sets of 3 replicas. Apigee recommends that you add 3 additional nodes to the Cassandra nodepool as standby worker nodes. To scale the number of Cassandra nodes down, see Scale down Cassandra.
Ingress/LoadBalancer	3rd-party proxy	Depends on the type of Ingress.
Logger	DaemonSet	DaemonSets manage replicas of a pod on all nodes, so they scale when you scale the pods themselves.
MART Synchronizer Metrics MPs	ApigeeDeployment (Custom CRD)	To scale on the command line, you can use the kubectl scale option. To scale via configuration, increase the value of the Deployment's replicaCountMin configuration property for the mart, synchronizer, metrics, or mp object. Deployments use a Horizontal Pod Autoscaler for autoscaling. Set the Deployment object's targetCPUUtilizationPercentage property to the threshold for scaling up; when this value is exceeded, Kubernetes adds pods up to the value of replicaCountMax. For more information on setting configuration properties, see Manage runtime plane components.
UDCA	ApigeeDeployment (Custom CRD)	To scale via configuration, increase the value of the udca object's replicaCountMin property in the overrides.yaml file. The UDCA service uses a Horizontal Pod Autoscaler for autoscaling. Set the udca object's targetCPUUtilizationPercentage property to the threshold for scaling up; when this value is exceeded, Kubernetes adds pods up to the value of replicaCountMax. For more information on setting configuration properties, see Manage runtime plane components.