yc serverless container revision deploy
Deploy new container revision
Command Usage
Syntax:
yc serverless container revision deploy (--container-id <CONTAINER_ID>|--container-name <CONTAINER_NAME>) [Flags...] [Global Flags...]
Flags
|
Flag |
Description |
|
|
Container id. |
|
|
Container name. |
|
|
Display information about the operation in progress, without waiting for the operation to complete. |
|
|
Required memory. Example: '1GB', '128MB'. The default value is 128MB. |
|
|
Number of cores that will be available to a container instance. |
|
|
If provided, specifies baseline performance for a core in percent. |
|
|
Execution timeout. The default value is 3s |
|
|
Set the maximum number of concurrent requests allowed per container instance. |
|
|
Service account id. |
|
|
Revision description. |
|
|
Revision environment variables. |
|
|
Image to run |
|
|
Comma-separated entrypoint for the container image. If not specified, the image's default ENTRYPOINT will be used. Pass an empty string to reset it to zero value. |
|
|
Comma-separated list of arguments that are passed to the command, run by a container. If not specified, the image's default CMD will be used. Pass an empty string to reset it to zero value. |
|
|
Revision secret. Possible property names:
|
|
|
Set the minimum number of concurrent instances. |
|
|
Upper limit for instances count in each zone. |
|
|
Upper limit for requests count in each zone. |
|
|
Network id to be used in new revision. |
|
|
Network name to be used in new revision. |
|
|
Specifies the subnets for the revision. Can use subnet names or subnet ids, or both. Example: `--subnets=id1,id2 --subnets=name3'. |
|
|
DEPRECATED: Use mounts instead. Storage mounts. Example: mount-point-path=/data,bucket=user-bucket,read-only=false Possible property names:
|
|
|
Add a mount to the revision. Example: type=ephemeral-disk,mount-point=/mnt/point,size=5GB Possible property names:
|
|
|
Container execution method. Valid values are 'http' and 'task'. |
|
|
Options set the access mode to revision's metadata endpoints. Example: aws-v1-http-endpoint=disabled,gce-http-endpoint=enabled Possible property names:
|
|
|
Disable logging from container. |
|
|
Send logs to custom log group by id. |
|
|
Send logs to custom log group by name. |
|
|
Send logs to default log group of custom folder by id. |
|
|
Send logs to default log group of custom folder by name. |
|
|
Min log level. Values: 'trace', 'debug', 'info', 'warn', 'error', 'fatal' |
|
|
Service account for asynchronous container invocation. |
Global Flags
|
Flag |
Description |
|
|
Set the custom configuration file. |
|
|
Debug logging. |
|
|
Debug gRPC logging. Very verbose, used for debugging connection problems. |
|
|
Disable printing user intended output to stderr. |
|
|
Enable gRPC retries. By default, retries are enabled with maximum 5 attempts. |
|
|
Set the ID of the cloud to use. |
|
|
Set the ID of the folder to use. |
|
|
Set the name of the folder to use (will be resolved to id). |
|
|
Set the Cloud API endpoint (host:port). |
|
|
Set the OAuth token to use. |
|
|
Set the ID of the service account to impersonate. |
|
|
Disable opening browser for authentication. |
|
|
Set the output format: text (default), yaml, json, json-rest. |
|
|
Query to select values from the response using jq syntax |
|
|
Display help for the command. |
- Добавить переменные окружения контейнеру
- Настройте асинхронный вызов
- Передать секреты Yandex Lockbox в контейнер
- Пример команды
- Создать ревизию контейнера
- Настроить параметры сервиса метаданных контейнера
- Смонтировать бакеты в контейнер
- Смонтировать эфемерный диск в контейнер
- Добавить настройки масштабирования контейнеру
- Удалить настройки масштабирования контейнера
- Изменить режим работы контейнера