Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Container Registry
  • Getting started
    • All guides
    • Installing and configuring Docker
    • Authentication in Container Registry
      • Getting information about existing lifecycle policies
      • Creating a lifecycle policy
      • Updating a lifecycle policy
      • Performing a lifecycle policy dry run
      • Deleting a lifecycle policy
    • Scanning Docker images for vulnerabilities
    • Creating a trigger for a registry
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Troubleshooting
  • FAQ

In this article:

  • Examples
  • Updating lifecycle policy rules
  • Updating a lifecycle policy status
  • Updating a lifecycle policy name
  • Updating a lifecycle policy description
  1. Step-by-step guides
  2. Managing Docker image lifecycle policies
  3. Updating a lifecycle policy

Updating a lifecycle policy

Written by
Yandex Cloud
Improved by
Danila N.
Updated at August 10, 2026
View in Markdown
  • Examples
    • Updating lifecycle policy rules
    • Updating a lifecycle policy status
    • Updating a lifecycle policy name
    • Updating a lifecycle policy description

After you create a lifecycle policy, you can edit its rules as well as its status, name, or description.

Management console
CLI
Terraform
API
  1. In the management console, select the folder with the registry.
  2. Navigate to Container Registry.
  3. Select the registry and click the row with its name.
  4. Select the repository and click the row with its name.
  5. In the left-hand panel, click Lifecycle.
  6. In the lifecycle policy row, click and select Edit.
  7. Edit the lifecycle policy settings:
    • Name.

    • Description.

    • Status.

    • Under Lifecycle policy rules, update the rule settings:

      • Tag regexp: Docker image tag for filtering. Java regular expressions are supported. For example, the test.* regular expression retrieves all images with tags starting with test.
      • Untagged: Flag to apply the rule to untagged Docker images.
      • Expire period, in days: Time after which the lifecycle policy may apply to the Docker image.
      • Retained top: Number of Docker images that will not be deleted even if they match the rule.
      • Description.
  8. Click Save.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

  1. See the description of the CLI command for updating policy settings:

    yc container repository lifecycle-policy update --help
    
  2. Update the policy settings, e.g., rename the policy:

    yc container repository lifecycle-policy update <policy_ID> \
       --new-name=new-policy
    

    To find out the policy ID, get a list of lifecycle policies in the repository or registry.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. Open the configuration file and edit the section describing the policy:

    resource "yandex_container_repository_lifecycle_policy" "my_lifecycle_policy" {
      name          = "best-policy"
      status        = "active"
      repository_id = "crpfvi6o4ra7********"
    
      rule {
        description   = "rule for applying policy"
        untagged      = true
        tag_regexp    = ".*"
        retained_top  = 1
        expire_period = "48h"
      }
    }
    
  2. Apply the changes:

    1. In the terminal, navigate to the configuration file directory.

    2. Make sure the configuration is correct using this command:

      terraform validate
      

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

      Success! The configuration is valid.
      
    3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

    4. Apply the configuration changes:

      terraform apply
      
    5. Type yes and press Enter to confirm the changes.

This will update the lifecycle policy in the specified repository. You can check the policy update using the management console or this CLI command:

yc container repository lifecycle-policy list --registry-id <registry_ID>

To update a lifecycle policy, use the Update method for the LifecyclePolicyService resource. Specify the policy ID in the lifecycle_policy_id property.

You can get the list of policies using the List method for the LifecyclePolicyService resource.

ExamplesExamples

Updating lifecycle policy rulesUpdating lifecycle policy rules

CLI
  1. Create new policy rules and save them to a file named new-rules.json.

    Example of the contents of a file with rules, where:

    • description: Description of the policy rule.
    • tag_regexp: Docker image tag for filtering. Java regular expressions are supported. For example, the test.* regular expression retrieves all images with tags starting with test.
    • untagged: Flag to apply the rule to untagged Docker images.
    • expire_period: Time after which the lifecycle policy may apply to the Docker image. This parameter comes as a number followed by a unit of measurement: s, m, h, or d (seconds, minutes, hours, or days). expire_period must be a multiple of 24 hours.
    • retained_top: Number of Docker images that will not be deleted even if they match the rule.
    [
      {
        "description": "delete prod Docker images older than 60 days but retain 20 last ones",
        "tag_regexp": "prod",
        "expire_period": "60d",
        "retained_top": 20
      },
      {
        "description": "delete all test Docker images except 10 last ones",
        "tag_regexp": "test.*",
        "retained_top": 10
      },
      {
        "description": "delete all untagged Docker images older than 48 hours",
        "untagged": true,
        "expire_period": "48h"
      }
    ]
    
  2. Update the current policy rules by running the command with the following parameter:

    • new-rules: Path to the file with the new policy description.

    Alert

    When you update the policy, all current rules are overwritten and deleted.

    yc container repository lifecycle-policy update crp6lg1868p3******** --new-rules ./new-rules.json
    

    Result:

    WARN: All current lifecycle rules will be overwritten. Are you sure?[y/N] y
    id: crp6lg1868p3********
    name: test-policy
    ...
      expire_period: 172800s
      tag_regexp: test.*
      untagged: true
    

Updating a lifecycle policy statusUpdating a lifecycle policy status

Activating a lifecycle policyActivating a lifecycle policy

CLI

To activate a disabled policy, run the command below with the --activate flag:

yc container repository lifecycle-policy update crp6lg1868p3******** --activate

Result:

id: crp6lg1868p3********
name: test-policy
repository_id: crp3cpm16edq********
...
  expire_period: 172800s
  tag_regexp: test.*
  untagged: true

Disabling a lifecycle policyDisabling a lifecycle policy

CLI

To disable an active policy, run the command below with the --disable flag:

yc container repository lifecycle-policy update crp6lg1868p3******** --disable

Result:

id: crp6lg1868p3********
name: test-policy
repository_id: crp3cpm16edq********
...
  expire_period: 172800s
  tag_regexp: test.*
  untagged: true

Updating a lifecycle policy nameUpdating a lifecycle policy name

CLI

Update the policy name by running this command:

yc container repository lifecycle-policy update crp6lg1868p3******** --new-name new-policy

Where --new-name is the new policy name. The naming requirements are as follows:

  • Length: between 3 and 63 characters.
  • It can only contain lowercase Latin letters, numbers, and hyphens.
  • It must start with a letter and cannot end with a hyphen.

Result:

id: crp6lg1868p3********
name: new-policy
repository_id: crp3cpm16edq********
...
  expire_period: 172800s
  tag_regexp: test.*
  untagged: true

Updating a lifecycle policy descriptionUpdating a lifecycle policy description

CLI

Update the policy description by running this command:

yc container repository lifecycle-policy update crp6lg1868p3******** --new-description "new description"

Where --new-description is the new policy description.

Result:

id: crp6lg1868p3********
name: test-policy
repository_id: crp3cpm16edq********
...
  expire_period: 172800s
  tag_regexp: test.*
  untagged: true

Was the article helpful?

Previous
Creating a lifecycle policy
Next
Performing a lifecycle policy dry run
© 2026 Direct Cursus Technology L.L.C.