Overview¶
CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.
Important
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 |
|---|---|
This add-on is a DNS server that provides domain name resolution for Kubernetes clusters through a chain add-on. | |
This add-on 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). | |
This add-on 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. It can run as a DaemonSet or a daemon. | |
This add-on resizes a cluster based on pod scheduling status and resource usage. | |
This add-on is an aggregator for monitoring data of core cluster resources. | |
This add-on is developed by CCE. It can be used to flexibly scale in or out Deployments based on metrics such as CPU usage and memory usage. | |
NVIDIA GPU is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers. | |
This add-on 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. |
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. |
Note
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.