Deployment Size¶

Deployment size sets the starting CPU, memory and replica count for every service on a runtime plane. You choose it once, when the plane is created, and it seeds the values each service starts with. Individual services can be tuned afterwards; the size itself cannot be changed.

There are three sizes: Small, Medium and Large.

The three sizes¶

Medium and Large carry the same replica counts. The two sizes differ in how much CPU and memory each pod gets, not in how many pods run. Choosing Large gives each service more capacity; it does not add more copies of it.

Solr redundancy moves with the pod count. At Medium and Large, Solr runs three pods and each collection keeps two copies of every shard (replicationFactor: 2), so losing a pod does not lose an index. At Small there is one Solr pod and one copy — a second copy has nowhere to go. Two copies also means each collection occupies roughly twice the index space it would at Small, spread across the pods' volumes, which is worth allowing for when sizing Solr storage.

How to set it¶

In the create wizard¶

Choose a size from the Deployment size dropdown on the first step of runtime plane creation. The control summarizes what the selected size changes as you switch between them.

Small is pre-selected. If you skip the field, the plane is created as Small.

Through the API¶

Set deploymentSize in the plane's runtimeConfigs when you create it:

1
2
3
4
5
6

{
  "runtimeConfigs": {
    "namespace": "my-plane",
    "deploymentSize": "MEDIUM"
  }
}

Accepted values are SMALL, MEDIUM and LARGE, case-insensitive. Any other value is rejected at creation rather than deploying something unintended. Deployment size applies to Self-Managed and Partially Managed (D2P) planes. It is not accepted on PrivaceraCloud planes, where Privacera manages the sizing for you.

What size does and does not change¶

It sets CPU requests and limits, memory requests and limits, and replica counts, for the services listed in the reference below. Values are applied when each service's configuration row is created, so services added to a plane later also pick up the plane's size.

It does not change:

• Storage. Volume sizes are identical at every size. Note that volumes are provisioned per replica, so a size that raises a replica count does raise total provisioned storage even though no individual volume grew.
• Observability sidecars. The otelClient and diagClient containers keep the same resources at every size.
• Ranger's replica count. Ranger runs a single replica at every size. Its database schema import is not safe to run concurrently, so the first start must have a single writer. Ranger can be scaled up safely once the plane is running and its schema exists.

Changing values after creation¶

Every value in the reference below is editable per service after the plane exists, under that service's Kubernetes Configs tab. Editing one service does not affect the others, and does not change the plane's recorded size.

Two constraints are worth knowing before you plan a change:

• Volume sizes cannot be reduced, and on a StatefulSet they generally cannot be changed at all once the workload exists. Size volumes before the first deploy on a plane you expect to carry heavy volume.
• Memory requests equal memory limits at Medium and Large, which makes those pods guaranteed QoS. A guaranteed pod needs a node with that much memory actually free, so a Medium or Large plane may need larger nodes — or a cluster autoscaler — where a Small plane schedules immediately.

Per-service reference¶

Values as shipped, generated from the service templates. Select a size to see every service at that size; the Small table is the baseline the other two are built from.

A dash means deployment size does not pin that property for the service, so it deploys at its chart default. Property names match the keys on each service's Kubernetes Configs tab.

Sidecar containers¶

Most services run one or two sidecars alongside the main container. Their resources are identical on every service that has them, and identical at all three sizes — deployment size does not touch them. They are listed once here rather than repeated under each service.

Other properties¶

Settings that belong to a single service — 27 rows across 2 services. Bold marks a value that differs from Small.