Cua Cloud Fleet Adds Declarative Pool Config via Terraform
- Source
- Cua
- Date
1/ Starting today: Infrastructure Field Notes - short clips from Robert, our Chief of Infra, explaining how we think about sandboxes and the systems behind them. First up: declarative configuration for sandbox pools in Cua Cloud Fleet 📷
2/ The shift is from scripting every provisioning step to declaring the pool state you want. One configuration describes the desired state; the system applies it.
3/ Pool sizing comes in two forms: - A static warm-pool target uses replicas. - Claim-driven scaling uses min_pool_size, initial_pool_size, and max_pool_size. Choose one and not both!
4/ Cua Fleet supports declarative pool configuration through its SDK and the public trycua/fleets Terraform provider. The guide covers reusable Linux and Windows pools, plus planning and security notes: https://t.co/7ERUQBqL51 Try Cua Fleet today: https://t.co/EIf47c6Z7f
- Cua Cloud Fleet lets teams declare the desired state of a pool in one configuration and have the system apply it, instead of scripting every provisioning step.
- Pool sizing is either a static warm-pool target via replicas or claim-driven scaling via min_pool_size, initial_pool_size and max_pool_size; Cua says to choose one, not both.
- Declarative configuration works through the Fleet SDK and the public trycua/fleets Terraform provider, with a guide covering reusable Linux and Windows pools plus planning and security notes.
Lets infrastructure teams manage sandbox pools as versioned Terraform config instead of one-off provisioning scripts.
Checking sign-in…
Loading comments…