tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
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
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
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
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
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

Component and Application Overview

PDF
Focus Mode
Font Size
Last updated: 2023-05-18 10:33:00

Add-on management description

TKE provides a variety of add-ons and rich cluster features to enhance cluster performance and overall stability. Three types of add-ons are available:
Add-On Type
Description
Documentation
System add-on
It is the default and core add-on in a cluster, such as CBS-CSI, IPAMD, monitoring add-on, and log add-on. If it is abnormal, the cluster may fail.
-
Enhanced add-on
It is also called the extended add-on, an extended feature package provided by TKE. You can select one as needed.
Application market
It provides Helm 3.0 features integrated by TKE and supports creating various products and services such as Helm charts, container images, and software services.
Note:
Disclaimer: Tencent Cloud supports your proper installation of applications from the application market for supported cluster types and Kubernetes versions, but is not responsible for other matters such as application issues during running, application exceptions due to custom configuration modification, or lack of support for specified cluster types and Kubernetes versions.
Tencent Cloud aftersales team provides applications from the application market specifically for experienced system admins or IT personnel. Tencent Cloud doesn't provide debugging or SLAs for such applications. If you encounter any problems when using an application, contact us via the reference link provided in the application details or at the official website of the application.
For more information on the TKE SLA, see Service Level Agreement.
The three types of add-ons are managed as follows:
Add-On Type
Scope
Service Level
Upgrade Method
System add-on(Default installation that cannot be deleted)
CBS-CSI, IPAMD, monitoring add-on, log add-on, etc.
TKE prioritizes the stability of system add-ons and promptly releases security and compatibility updates and fixes on the backend.
TKE will not update certain versions with special features, which need to be manually updated as needed. For detailed directions, see Add-On Version Maintenance Description.
Enhanced add-on(Custom installation)
For more information on the list, see Add-on Overview.
TKE guarantees the stability of enhanced add-ons and promptly releases security and compatibility updates and fixes on the backend. Each enhanced add-on comes with a list of supported versions and may fail if you don't update it promptly.
TKE will not update certain versions with special features, which need to be manually updated as needed. For detailed directions, see Add-On Version Maintenance Description.
Application market(Custom installation)
For more information on the list, see here.
TKE only supports the installation and deployment of applications for supported cluster types and Kubernetes versions.
TKE provides application update methods and may push new charts from time to time. For detailed directions, see Use the application.

Feature management description

Certain features are identified as "preview" by TKE in the documentation and in the console, indicating that they are try-outs and are not covered by the Service Level Agreement.


Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback