Adding a container label

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the documentation on the Terraform website or mirror website.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

To add a label to a container created using Terraform:

1. Open the Terraform configuration file and add the labels section to the yandex_serverless_container resource:

   ...
   resource "yandex_serverless_container" "test-container" {
     name   = "my first container with description"
     memory = 256
     image {
        url = "cr.yandex/yc/test-image:v1"
     }
     labels = {
        label1 = "test"
     }
   }
   ...
   

   For more information about the yandex_serverless_container resource parameters in Terraform, see the provider documentation.

2. Check the configuration using this command:

   terraform validate
   

   If the configuration is correct, you will get this message:

   Success! The configuration is valid.
   

3. Run this command:

   terraform plan
   

   The terminal will display a list of resources with parameters. No changes will be made at this step. If the configuration contains any errors, Terraform will point them out.

4. Apply the configuration changes:

   terraform apply
   

5. Confirm the changes: type yes into the terminal and press Enter.

You can verify that you have created the container labels using the CLI:

yc serverless container get <container_name_or_ID>

To add a container label, use the update REST API method for the Container resource or the ContainerService/Update gRPC API call.