Tencent Container Registry
- Updates and Announcements
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Access Configuration
- Credential Access Control
- Network Access Control
- Access Permission Configuration
- Access Domain Name Configuration
- Manage Image Repository
- Image Distribution
- Image Security
- Synchronization and Replication
- DevOps
- OCI Artifacts Management
- Operation Guide for TCR Individual
- Configuring Access Permission
- Practical Tutorial
- API Documentation
- Making API Requests
- Instance Management APIs
- Namespace APIs
- Access Control APIs
- Instance Synchronization APIs
- Tag Retention APIs
- Trigger APIs
- Helm Chart APIs
- Image Repository APIs
- Custom Account APIs
- Related Agreement
Release Notes
Last updated: 2024-12-02 14:22:39
Note:
This document describes the updates to Tencent Container Registry (TCR) Enterprise Edition. For more information about the updates to Tencent Kubernetes Engine (TKE), see Release Notes.
March 2023
Update | Description | Reference |
Service accounts | The access credential feature is upgraded to support both user accounts and service accounts. Users can create and manage service accounts with a custom username, password, permission, and expiration time. The management of instance permissions are simplified, which makes the feature suitable for systems that supports continuous integration and continuous deployment (CI/CD). | - |
COS multi-AZ | This feature is optional. When you create a TCR Enterprise Edition instance, we recommend that you enable the COS multi-AZ feature to achieve multi-AZ disaster recovery for higher data reliability and service availability. This feature incurs higher storage costs. |
December 2022
Update | Description | Reference |
Reuse of TCR Individual domain names | Shared TCR Individual Edition domain names can be reused in exclusive TCR Enterprise Edition instances. This allows you to push images to or pull images from an exclusive TCR Enterprise Edition instance by using the URL of a TCR Individual Edition image repository. This way, the costs of upgrading to TCR Enterprise Edition instances are reduced. |
September 2022
Update | Description | Reference |
Image signing | The container image signing feature is launched to ensure image consistency across the entire linkage. | |
Increased number of accessed VPCs | The quota for connected VPCs is increased for all versions. Up to 20 VPCs can be connected. | - |
Feature of checking whether a domain name has an ICP filing | The feature of checking whether a domain name has an ICP filing is added for custom domain names to meet compliance requirements. | - |
June 2022
Update | Description | Reference |
Quick start | Users can quickly initialize TCR Enterprise instances that are newly created in five minutes to push your first container image. | - |
Improved image retention capability | Advanced configuration is added to the image retention feature of TCR Enterprise Edition. The feature allows you to configure image filtering rules, which support regular expressions. |
December 2021
Update | Description | Reference |
Upgrade of image acceleration to download data in an image on demand | The capability of image acceleration is upgraded. It can be enabled with one click. The container can be started in seconds when deploying the application, without the need to pull all image data. | |
Automatic image deployment in all regions in TCR Individual service | The TCR Individual service supports the automatic image deployment feature based on CODING DevOps in all available regions, which can automatically trigger image building for code push and automatically push images to the Individual Edition image repository to update container applications in the specified cluster. | - |
November 2021
Update | Description | Reference |
Image building in all regions in TCR Individual service | The TCR Individual service supports image building based on CODING DevOps in all available regions. You can select the specified image repository in the unified product console to implement image building. | - |
New entry of TCR Individual in the console | Starting from November 1, 2021 (UTC +8), entry of TCR Individual (the original path: TKE > Image Repository) in the console will be changed to be located in the TCR console and this will be in beta testing. For the relationship of the existing features in the two consoles, see related documents. |
October 2021
Update | Description | Reference |
Check of instance replication logs | The instance replication feature now supports checking replication logs, and supports querying via API. | |
Unified management of image repositories of TCR Individual | The TCR console now supports unified management of image repositories of TCR Individual. Users can view TCR Individual instances, and manage namespaces and image repositories. | - |
July 2021
Update | Description | Reference |
Cross-master account instance synchronization | The instance synchronization feature supports cross-master account synchronization of instance data. | |
Image tag immutability | The tag immutability feature can be enabled for images hosted in TCR, which ensures that images of the same tag will only be successfully pushed once. |
June 2021
Update | Description | Reference |
Enhanced TCR console features | The original instance list page has been upgraded to an instance management page, where you can view the instance overview, the latest TCR features, and product updates. | - |
Batch adding/editing for the public network access allowlist | The TCR console supports entering multiple IP addresses or IP ranges in the allowlist at a time or importing the configurations of an existing security group. | |
Multiple supported regions added for auto-parsing management | Nanjing, Hong Kong (China), Singapore, Frankfurt, Chengdu, and Chongqing are added as the supported regions. | |
Removal of unused image data | Users can set custom rules to remove unused image data of TCR Enterprise Edition instances in batches to release storage capacity. Dry runs are supported. |
April 2021
Update | Description | Reference |
Querying audit logs | TCR Enterprise has been integrated with Tencent CloudAudit. Users can check the logs of read and write operations of instances, namespaces, and image repositories in "Event History". | - |
March 2021
Update | Description | Reference |
Custom domain names | TCR supports custom domain names. User can add custom domain names and SSL certificates to a TCR Enterprise Edition instance, and access the instance through the HTTPS protocol. |
January 2021
Update | Description | Reference |
Multi-region replication of a single instance | Users can create replicas of an Enterprise Premium instance in multiple regions with the same access domain name and credential as the original TCR Enterprise Edition instance and synchronize underlying image data of the original instance to replicas in real time. After image data is uploaded, it can be downloaded through the local private network in multiple regions. | |
Compatibility with cloud-native artifacts and multi-architecture images | TCR Enterprise instances are compatible with cloud-native artifacts (OCI). Image Registry can host Helm charts, CNAB, and other cloud-native artifacts. TCR Enterprise Edition instances can host multi-architecture container images, such as AMD64 and ARM, to be applicable to IoT and edge computing scenarios. | - |
Added support for on-demand container image loading | A TCR Enterprise Premium instance can enable the on-demand container image loading feature. When cluster nodes pull image data from the TCR Enterprise Premium instance, they can mount pulled data as needed, improving the container startup speed. | |
Optimized private network access feature | When a private network access linkage is created for an instance deployed in China, the VPCDNS can be used to configure private network resolution for the instance access domain name, without the need to use an external DNS or configure the host. | |
TCR Enterprise available in the Taipei (China) region | TCR Enterprise is now available in the Taipei (China) region. For more information on billing, see Billing Overview. |
December 2020
Update | Description | Reference |
Commercial billing for TCR Enterprise | TCR Enterprise Edition instances have ended beta testing and will be billed. SLA guarantees are provided, and users can purchase instances in pay-as-you-go mode. | |
TCR Enterprise available in Virginia and Frankfurt regions | TCR Enterprise is now available in the Virginia and Frankfurt regions. For more information on billing, see Billing Overview. |
October 2020
Update | Description | Reference |
Added support for multiple code sources in the image building feature | The private GitLab and TGit code sources are now supported, and the code source authorization process has been optimized. | - |
Image filtering in the delivery pipeline deployment feature | Local push images can be used to trigger the deployment process, and filtering rules can be configured to deploy only the most recently pushed images that meet the rules. |
September 2020
Update | Description | Reference |
Image tag retention feature | Automatic clearing rules can be configured for image tags in a namespace to periodically clear historical image tags. |
August 2020
Update | Description | Reference |
TCR add-on available in TKE clusters | You can quickly install the TCR Enterprise add-on in a TKE cluster to enable secret-free pulling of container images and Helm charts through the private network. This significantly improves the application deployment experience. | |
Tencent Cloud tags | Users can bind TCR Enterprise Edition instances with Tencent Cloud tags, with which they can perform instance resource filtering and permission management. |
July 2020
Update | Description | Reference |
Delivery pipeline feature | After a delivery pipeline is configured, code updates can automatically trigger image building, image push, and application updates. When used with TKE, this feature can quickly implement container DevOps. | |
Updated Helm chart feature | Users can upload and download chart packages through the console. TKE can use TCR private Helm repositories for application deployment. |
June 2020
Update | Description | Reference |
Full beta test for TCR Enterprise | TCR Enterprise officially starts a full beta test. Users can create secure and exclusive TCR Enterprise Edition instances and use image security scanning, cross-region instance synchronization, and Helm chart hosting. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No