Release Notes and Announcements
- Release Notes
- Announcements
- Release Notes
Product Introduction
Purchase Guide
- Purchase Instructions
- Purchase a TKE General Cluster
- Purchasing Native Nodes
- Purchasing a Super Node
Getting Started
Cluster Configuration
- General Cluster Overview
- Cluster Management
- Network Management
- Storage Management
- Node Management
- GPU Resource Management
- Remote Terminals
Application Configuration
- Workload Management
- Service and Configuration Management
- Component and Application Management
- Auto Scaling
- Container Login Methods
Observability Configuration
- Ops Observability
- Cost Insights and Optimization
Scheduler Configuration
- Scheduling Component Overview
- Resource Utilization Optimization Scheduling
- Business Priority Assurance Scheduling
- QoS Awareness Scheduling
Security and Stability
- TKE Security Group Settings
- Identity Authentication and Authorization
- Application Security
- Cluster Security Enhancement Capability
Multi-cluster Management
- Planned Upgrade
- Backup Center
Cloud Native Service Guide
- Cloud Service for etcd
- TMP
- TKE Serverless Cluster Guide
- TKE Registered Cluster Guide
Use Cases
- Cluster
- Serverless Cluster
- Scheduling
- Security
- Service Deployment
- Network
- Release
- Logs
- Monitoring
- OPS
- Terraform
- DevOps
- Auto Scaling
- Containerization
- Cost Management
- Hybrid Cloud
- AI
Troubleshooting
API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Elastic Cluster APIs
- Resource Reserved Coupon APIs
- Cluster APIs
- Third-party Node APIs
- Relevant APIs for Addon
- Node Pool APIs
- Network APIs
- Node APIs
- Node Pool APIs
- TKE Edge Cluster APIs
- Cloud Native Monitoring APIs
- Scaling group APIs
- Super Node APIs
- Other APIs
- Data Types
- Error Codes
- TKE API 2022-05-01
FAQs
- TKE General Cluster
- TKE Serverless Cluster
- About OPS
- Hidden Danger Handling
- About Services
- Image Repositories
- About Remote Terminals
- Event FAQs
- Resource Management
Service Agreement
- TKE Service Level Agreement
- TKE Serverless Service Level Agreement
Contact Us
Glossary

TCR (Tencent Container Registry)

Download

Modo Foco

Tamanho da Fonte

Última atualização: 2026-08-14 15:09:36

Traduzido por IA

Component Introduction
The TCR (Tencent Container Registry) integration component provides connectivity between TKE clusters and TCR Enterprise Edition instances. It supports automatic node authentication to TCR image repositories, eliminating the need for the cumbersome manual configuration of imagePullSecrets.
Main Features:
Automatic Authentication: Pods within the cluster can directly pull private images from TCR Enterprise Edition without manually configuring Secrets.
Multi-Repository Support: It supports binding to multiple TCR Enterprise Edition instances simultaneously.
Access Acceleration: It supports accessing TCR via a private network, reducing image pull latency and public network bandwidth consumption.
For component details, see TCR Description.
Change Records
Release Date
Version Number
Change Content
Limitations and Impacts
2026-05-07
1.0.6
Support for the ARM architecture (amd64/arm64 dual-architecture) has been added.
Support for taint toleration has been added to the apparate workload within the component.
The excludedNamespaces field of the Webhook supports system namespaces such as kube-system and kube-public by default.
None
2026-02-09
1.0.5
When images are pulled from TCR without a password, the namespaces exempted by the Pod Webhook by default can be specified externally.
Support for handling ServiceAccount Update events has been added.
None
2026-01-18
1.0.4
The TCR component Pod uses tcr-assistant-sa instead of the default ServiceAccount.
Fixed the issue where specifying an ImagePullSecret separately when creating a Pod in TKE caused image pull failures.
ServiceAccount used by newly added components in the cluster
2026-01-15
1.0.3
Added a Webhook for Pod creation detection and fixed the occasional timing issue with credential injection in ServiceAccounts.
Addition of a Webhook (deployed in the same Pod as the TCR component) and related Webhook rule configurations within the cluster.
2025-09-17
1.0.2
Fixed the issue of missing logs.
None
2025-03-17
1.0.0
Initial release, supporting automatic authentication for TCR Enterprise Edition and private network access acceleration.
The cluster must have VPC private network access enabled during installation.
﻿

Ajuda e Suporte

Esta página foi útil?

Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.

comentários

tencent cloud

Tencent Kubernetes Engine

TCR (Tencent Container Registry)

Component Introduction

Change Records

Ajuda e Suporte

Release Date	Version Number	Change Content	Limitations and Impacts
2026-05-07	1.0.6	Support for the ARM architecture (amd64/arm64 dual-architecture) has been added. Support for taint toleration has been added to the apparate workload within the component. The excludedNamespaces field of the Webhook supports system namespaces such as kube-system and kube-public by default.	None
2026-02-09	1.0.5	When images are pulled from TCR without a password, the namespaces exempted by the Pod Webhook by default can be specified externally. Support for handling ServiceAccount Update events has been added.	None
2026-01-18	1.0.4	The TCR component Pod uses tcr-assistant-sa instead of the default ServiceAccount. Fixed the issue where specifying an ImagePullSecret separately when creating a Pod in TKE caused image pull failures.	ServiceAccount used by newly added components in the cluster
2026-01-15	1.0.3	Added a Webhook for Pod creation detection and fixed the occasional timing issue with credential injection in ServiceAccounts.	Addition of a Webhook (deployed in the same Pod as the TCR component) and related Webhook rule configurations within the cluster.
2025-09-17	1.0.2	Fixed the issue of missing logs.	None
2025-03-17	1.0.0	Initial release, supporting automatic authentication for TCR Enterprise Edition and private network access acceleration.	The cluster must have VPC private network access enabled during installation.