POST /accounts/{account_id}/containers/applications/{application_id}/rollouts

Account identifier.

Default value: "application/json"

Properties required to modify a cloudchamber deployment specified by the user.

The instance type will be used to configure vCPU, memory, and disk.

• "lite": 1/16 vCPU, 256 MiB memory, 2 GB disk
• "basic": 1/4 vCPU, 1 GiB memory, 4 GB disk
• "standard-1": 1/2 vCPU, 4 GiB memory, 8 GB disk
• "standard-2": 1 vCPU, 6 GiB memory, 12 GB disk
• "standard-3": 2 vCPU, 8 GiB memory, 16 GB disk
• "standard-4": 4 vCPU, 12 GiB memory, 20 GB disk

Default value: "lite"

Deployment labels

A label name

A label value

The command to be executed when the container starts, passed to the entrypoint. This can be overridden at run-time. If only the command is overridden at run-time, it gets passed to the default entrypoint specified in the image.

Lifecycle configuration for a deployment.

Duration string. From Go documentation: A string representing the duration in the form "3d1h3m". Leading zero units are omitted. As a special case, durations less than one second format use a smaller unit (milli-, micro-, or nanoseconds) to ensure that the leading digit is non-zero.

Image url

Specify the memory to be used for the deployment, in MiB. The default will be the one configured for the account.

Settings for deployment observability such as logging.

Observability logging settings.

Default value: false

Specify the vcpu to be used for the deployment. Vcpu must be at least 1. The input value will be rounded to the nearest 0.0001. The default will be the one configured for the account.

A list of SSH public key IDs from the account

A memory size that specifies its unit at the end.

Configuration properties for SSH'ing into a container with Wrangler

Default value: 22

Default value: true

A list of objects with secret names and the their access types from the account

The name of the secret within the container

The secret access type denotes how a secret is made available within a container. Available Options are "env".

Valid values:

• "env"

Corresponding secret name from the account

Optional human readable name for this key

An SSH public key

Container environment variables

An environment variable name

An environment variable value

Opt-in experimental flags for this application. Only a subset of experimental flags can be set by users; unsupported values are rejected.

The entry point for the container, specifying the executable to run when the container starts. This can be overridden at run-time. If overridden, the default command from the image is ignored. Both entrypoint and command can be specified at run-time to completely replace the image defaults.

Configuration for enabling the container metadata service.

Whether the metadata service should be enabled for the deployment.

Optional human readable name for this key

An SSH public key

The disk configuration for this deployment. By default, all containers have a disk size of 2GB.

A disk size that specifies its unit at the end.

Size of the disk, in MB.

Represents the /etc/resolv.conf that will appear in the deployment. If the 'dns' property is specified, even if empty object, will override the default resolv.conf of the container. The default resolv.conf of a container is 'servers = ["1.1.1.1", "9.9.9.9", "2606:4700:4700::1111"]', only if an IPv4 is assigned. The default for a non IPv4 deployment is 'servers = ["2606:4700:4700::1111", "2620:fe::fe"]'.

List of DNS servers that the deployment will use to resolve domain names. You can only specify a maximum of 3.

The container resolver will append these domains to every resolve query. For example, if you have 'google.com', and your deployment queries 'web', it will append 'google.com' to 'web' in the search query before trying 'web'. Limited to 6 domains.

Initial target version percentage (0-100). Version sync will actively replace instances to match. Required when strategy is "new_instances" and kind is "full_manual". When strategy is "new_instances" and kind is "full_auto", omitted percentage starts at 10% or the smallest percentage that targets at least one instance. Not used for "rolling".

Description of the rollout process.

Percentage of rollout to increase in each step when "steps" is not specificed. Applicable values are 5, 10, 20, 25, 50, 100. These create rollouts with 20, 10, 5, 4, 2, 1 steps respectively. Only valid for "rolling" strategy.

Valid values:

• 100
• 25
• 5
• 50
• 20
• 10

Steps defining the rollout process, when "step_percentage" is not defined. Only one of "step_percentage" or "steps" can be defined when creating a rollout. "steps" allow granular control over each step. Only valid for "rolling" strategy.

Percentage of instances affected in this step. Min 10% and Max 100%.

Description of the rollout step.

Strategy used for the rollout.

• "rolling": Step-based rollout with health gates. Actively replaces instances to reach each step's target percentage.
• "new_instances": Percentage control over version distribution. Version sync actively replaces instances to match the configured percentage. The "full_auto" kind advances through fixed percentage targets after target-version health is observed.

Valid values:

• "rolling"
• "new_instances"

Kind of the rollout process.

• "full_auto": For rolling rollouts, starts progressing steps upon rollout creation. For new_instances rollouts, advances percentage targets automatically after target-version health is observed.
• "full_manual": Requires manually progressing each step in the rollout using the UpdateRollout's action paramater. For "new_instances" strategy, omit "kind" to preserve manual percentage behavior, or set "full_auto" to start an automatic 10% health-gated ramp.

Valid values:

• "full_auto"
• "full_manual"