Overview
CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.
CCE uses Helm charts to deploy add-ons. To modify or upgrade an add-on, perform operations on the Add-ons page or use open add-on management APIs. Do not directly modify resources related to add-ons in the background. Otherwise, add-on exceptions or other unexpected problems may occur.
Add-on Name |
Description |
---|---|
CoreDNS is a DNS server that provides domain name resolution for Kubernetes clusters through a chain add-on. |
|
CCE storage add-on Everest is a cloud native container storage system, which enables clusters of Kubernetes v1.15.6 or later to use cloud storage through the Container Storage Interface (CSI). |
|
CCE node problem detector (NPD) is an add-on that monitors abnormal events of cluster nodes and connects to a third-party monitoring platform. It is a daemon running on each node. It collects node issues from different daemons and reports them to the API server. The NPD add-on can run as a DaemonSet or a daemon. |
|
Kubernetes Dashboard is a general-purpose, web-based UI for Kubernetes clusters and integrates all commands that can be used in the CLI. It allows users to manage applications running in a cluster and troubleshoot faults, as well as manage the cluster itself. |
|
The Autoscaler add-on resizes a cluster based on pod scheduling status and resource usage. |
|
metrics-server is an aggregator for monitoring data of core cluster resources. |
|
cce-hpa-controller is a CCE-developed add-on, which can be used to flexibly scale in or out Deployments based on metrics such as CPU usage and memory usage. |
|
Prometheus is an open-source system monitoring and alerting framework. CCE allows you to quickly install Prometheus as an add-on. |
|
NVIDIA GPU is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers. |
|
NVIDIA GPU is a device management add-on that supports Huawei NPUs in containers. |
|
Volcano is a scheduler for general-purpose, high-performance computing such as job scheduling, heterogeneous chip management, and job running management, serving end users through computing frameworks for different industries such as AI, big data, gene sequencing, and rendering. |
|
Nginx Ingress controller forwards application data such as the data of virtual hosts, load balancers, SSL proxy, and HTTP routing for Services that can be directly accessed outside a cluster. |
|
The dew-provider add-on is used to interconnect with Data Encryption Workshop (DEW), which allows you to mount secrets stored outside a cluster (DEW for storing sensitive information) to pods. In this way, sensitive information can be decoupled from the cluster environment, which prevents information leakage caused by program hardcoding or plaintext configuration. |
|
dolphin is an add-on for monitoring and managing container network traffic. This add-on collects how many IPv4 packets and bytes are received and sent (including those sent to the Internet) and allows you to obtain pod labels. dolphin supports multiple monitoring tasks, allows you to select monitoring metrics, and uses a PodSelector to select monitoring backends. The monitoring information has been adapted to Prometheus. You can call the Prometheus API to view monitoring data. |
|
NodeLocal DNSCache improves cluster DNS performance by running DNS cache proxies as DaemonSets on cluster nodes. |
Add-on Lifecycle
An add-on lifecycle involves all the statuses of the add-on from installation to uninstallation.
Status |
Attribute |
Description |
---|---|---|
Running |
Stable state |
The add-on is running properly, all add-on instances are deployed properly, and the add-on can be used properly. |
Partially ready |
Stable state |
The add-on is running properly, but some add-on instances are not properly deployed. In this state, the add-on functions may be unavailable. |
Unavailable |
Stable state |
The add-on malfunctions, and all add-on instances are not properly deployed. |
Installing |
Intermediate state |
The add-on is being deployed. If all instances cannot be scheduled due to incorrect add-on configuration or insufficient resources, the system sets the add-on status to Unavailable 10 minutes later. |
Installation failed |
Stable state |
Install add-on failed. Uninstall it and try again. |
Upgrading |
Intermediate state |
The add-on is being upgraded. |
Upgrade failed |
Stable state |
Upgrade add-on failed. Upgrade it again, or uninstall it and try again. |
Rolling back |
Intermediate state |
The add-on is rolling back. |
Rollback failed |
Stable state |
The add-on rollback failed. Retry the rollback, or uninstall it and try again. |
Deleting |
Intermediate state |
The add-on is being deleted. If this state stays for a long time, an exception occurred. |
Deletion failed |
Stable state |
Delete add-on failed. Try again. |
Unknown |
Stable state |
No add-on chart found. |
When an add-on is in an intermediate state such as Installing or Deleting, you are not allowed to edit or uninstall the add-on.
If the add-on status is unknown and the returned status.Reason is "don't install the addon in this cluster", the secret associated with the Helm release of the add-on in the cluster is typically deleted by mistake. In this case, uninstall the add-on and reinstall it with the same configurations.
Related Operations
Operation |
Description |
Procedure |
---|---|---|
Install |
Install a specified add-on. |
|
Upgrade |
Upgrade an add-on to the new version. |
|
Edit |
Edit add-on parameters. |
|
Uninstall |
Uninstall an add-on from the cluster. |
|
Roll back |
Roll back an add-on to the source version.
NOTE:
|
|
Add-on rollback is supported in certain add-on versions.
- CoreDNS: 1.25.11 and later versions
- Everest: 2.1.19 and later versions
- Autoscaler:
- v1.21 clusters: v1.21.22 and later versions
- v1.23 clusters: v1.23.24 and later versions
- v1.25 clusters: v1.25.14 and later versions
- kube-prometheus-stack: v3.7.2 and later versions
- Volcano: 1.11.4 and later versions
- NPD: 1.18.22 and later versions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot