Names and limits
Naming rules for container instances and their parts, the limits that apply to them, and the compute plans.
Names
| Name | Rules |
|---|---|
| Instance | Lowercase letters, digits and hyphens, not starting or ending with a hyphen; 3 to 50 characters in the portal, up to 63 through the API. Unique in the resource group; cannot be changed. Start it with a letter — see Basics. |
| Component, container, volume, endpoint | Lowercase letters, digits and hyphens, starting with a letter and not ending with a hyphen; at most 63 characters. Unique in the instance (components, endpoints) or in the component (containers and init containers together, volumes). Cannot be changed once saved. |
| Port | The same, at most 15 characters, unique in the component. Cannot be changed once saved. |
| Environment variable | Letters, digits, _, - and ., not starting with a digit; unique in the container. A vault-backed name is unique in the component. |
File in a files volume |
Letters, digits, ., _ and -. |
Derived names — <instance>-<component> for the in-cluster name, the platform hostname — longer
than 63 characters are shortened, and a short hash is added to keep them unique.
Limits
| What | Limit |
|---|---|
| Components per instance | 16 |
| Containers per component | 8, plus 4 init containers |
| Volumes per component | 8 |
| Ports per component | 32, across its containers |
| Endpoints per instance | 12 |
| Replicas per component | 0 to 10; 0 or 1 with a persistent volume |
| Environment variables per container | 128; a value at most 32 768 characters |
| Command | 64 elements; arguments 128; each at most 4 096 characters |
Files per files volume |
16 files, 900 KiB per volume, 1 MiB across the instance |
| Upload on the Files tab | 512 MiB per file |
Compute plans
A plan sizes a whole component. Its CPU and memory are divided between the component's main containers, and each container is limited to exactly its share.
| Plan | CPU | Memory | Described as |
|---|---|---|---|
nano |
100m (0.1 CPU) | 128Mi | Minimal resources for lightweight workers and testing |
small |
250m | 256Mi | Small services and background workers |
medium |
500m | 1Gi | Standard services for small production workloads |
large |
2000m (2 CPU) | 4Gi | Resource-intensive services and high-throughput workers |
A boundary can restrict which plans its instances may use; see Change the compute plan.