Deleting container scaling settings
- In the management console
, select the folder with your container. - Go to Serverless Containers.
- Select the container.
- Navigate to the Editor tab.
- Under Settings, specify:
- Number of prepared instances:
0. - Number of container instances in availability zone:
0. - Number of concurrent container invocations in availability zone:
0.
- Number of prepared instances:
- Click Create revision.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.
To delete scaling settings, create a new container revision without specifying scaling settings:
yc serverless container revision deploy \
--container-id <container_ID> \
--image <Docker_image_URL> \
--service-account-id <service_account_ID>
Where:
--container-id: Container ID. To find out the ID, get the list of containers.--image: Docker image URL.--service-account-id: ID of the service account authorized to download the image.
Result:
done (2s)
id: bbam2cv903iv********
container_id: bbab5i36nvda********
created_at: "2026-04-01T13:31:11.459Z"
image:
image_url: cr.yandex/crpp35hht729********/ubuntu:hello
image_digest: sha256:f6f34c6cf5f56e594e9828274592f1cc4d9383b1689057ccaf188d41********
resources:
memory: "134217728"
cores: "1"
core_fraction: "100"
execution_timeout: 3s
concurrency: "1"
service_account_id: aje07l4q4vmo********
status: ACTIVE
log_options:
folder_id: b1gc1t4cb638********
runtime:
http: {}
metadata_options: {}
To learn more about the command, see the CLI reference.
To delete container scaling settings, use the deployRevision REST API method for the Container resource or the ContainerService/DeployRevision gRPC API call.