Scaling

The ITX Launcher Server pods run independently of each other and process client requests and triggered flows in a load balanced way. To access the same set of compiled maps and system flows, the pods may either access a shared persistent data volume, where the compiled maps and systems are saved, or download all runtime artifacts from Cloud Object Storage. Cloud Object Storage may work with either a persistent data volume or ephemeral storage, which enables a stateless deployment with no single point of failure.

The number of pods running at any time can be controlled through the replicaCount or autoscaling settings that are exposed in the values.yaml file. When sufficient system resources are provisioned for newly added pods, the deployment will be better able to handle increased workloads in a resilient and load balanced way.