Backups in Serverless Containers
Data in Serverless Containers is stored securely and replicated within the Yandex Cloud infrastructure. You can get:
- List of containers.
- Container revision lists.
- Information about container revisions.
- Lists of triggers.
- Information about triggers.
For more information about backing up Docker images used to create container revisions, see the Yandex Container Registry documentation.
Getting a container list
- In the management console
, go to the folder where you want to view a list of containers. - Select Serverless Containers.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To get a list of containers, run the following command:
yc serverless container list
Result:
+----------------------+--------------------+-----------------------+--------+
| ID | NAME | FOLDER ID | STATUS |
+----------------------+--------------------+-----------------------+--------+
| b097d9ous3ge******** | my-beta-container | aoek49ghmknn******** | ACTIVE |
+----------------------+--------------------+-----------------------+--------+
To view a list of containers, use the list REST API method for the Container resource or the ContainerService/List gRPC API call.
Getting a container revision list
- In the management console
, select the folder with your container. - Select Serverless Containers.
- Select the container to get a list of revisions for.
- Under Revisions, you can find the list of container revisions and their details.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To find out the name or unique ID of a container, get a list of containers in the folder.
To get a list of container revisions, run this command:
yc serverless container revision list --container-name <container_name>
Result:
+----------------------+----------------------+--------------------------------------------+---------------------+
| ID | CONTAINER ID | IMAGE | CREATED AT |
+----------------------+----------------------+--------------------------------------------+---------------------+
| bbaq84v92qqc******** | bbab5i36nvda******** | cr.yandex/crpp35hht729********/ubuntu:test | 2021-09-09 11:22:28 |
| bba5eosk5sod******** | bbab5i36nvda******** | cr.yandex/crpp35hht729********/ubuntu:test | 2021-09-09 10:13:04 |
+----------------------+----------------------+--------------------------------------------+---------------------+
To get a list of container revisions, use the listRevisions REST API method for the Container resource or the ContainerService/ListRevisions gRPC API call.
Getting information about a container revision
- In the management console
, select the folder with your container. - Select Serverless Containers.
- Select the container to get revision information for.
- Under Revisions, you can find the list of container revisions and their details.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To find out the name or unique ID of a container revision, get a list of container revisions in the folder.
To get detailed information about a container revision, run this command:
yc serverless container revision get <revision_ID>
Result:
id: bbaq84v92qqc********
container_id: bbab5i36nvda********
created_at: "2021-09-09T11:22:28.128Z"
image:
image_url: cr.yandex/crpp35hht729********/ubuntu:test
image_digest: sha256:9f05670784f562f278177e43a9ae0179f29b3cb93b2ef165b935f1k9********
resources:
memory: "1207959552"
cores: "1"
core_fraction: "100"
execution_timeout: 0s
concurrency: "1"
service_account_id: aje07l4q4vmo********
status: ACTIVE
To get information about a container revision, use the getRevision REST API method for the Container resource or the ContainerService/GetRevision gRPC API call.
Getting a list of triggers
- In the management console
, go to the folder where you want to view a list of triggers. - Open Serverless Containers.
- In the left-hand panel, select
Triggers.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
Get a list of triggers:
yc serverless trigger list
Result:
+----------------------+------------+----------------------+
| ID | NAME | FOLDER ID |
+----------------------+------------+----------------------+
| dd0gj5tsj2p3******** | my-trigger | aoek49ghmki7******** |
+----------------------+------------+----------------------+
To get a list of triggers, use the list REST API method for the Trigger resource or the TriggerService/List gRPC API call.
Getting information about a trigger
- In the management console
, select the folder containing your trigger. - Open Serverless Containers.
- In the left-hand panel, select
Triggers. - Select the trigger you want to get details about.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
Get detailed information about a trigger:
yc serverless trigger get <trigger_name>
Result:
id: a1sfe084v4h2********
folder_id: b1g88tflrih2********
created_at: "2022-12-04T08:45:31.131391Z"
name: mail-trigger
description: My trigger for mail.
rule:
mail:
email: a1smdtklemh2********-xivn****@serverless.yandexcloud.net
invoke_container:
container_id: bba5jb38o8h2********
service_account_id: aje03adgd2h2********
retry_settings:
retry_attempts: "1"
interval: 10s
dead_letter_queue:
queue-id: yrn:yc:ymq:ru-central1:b1gmit33ngh2********:dlq
service-account-id: aje3lebfemh2********
status: ACTIVE
To get information about a trigger, use the get REST API method for the Trigger resource or the TriggerService/Get gRPC API call.