Overview¶
CCE provides multiple types of add-ons to manage extended cluster functions. You can select add-ons as required to enhance the functions and flexibility of containerized applications.
These add-ons include CCE-developed and enhanced add-ons and widely used open-source add-ons.
CCE-developed and enhanced add-ons are deeply integrated into CCE and optimized for specific service requirements and scenarios. They can better support complex enterprise applications and ensure high performance and reliability.
Open-source add-ons leverage extensive community support and mature technologies to provide users with various functions and flexible solutions to meet ever-changing service requirements.
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. Avoid making changes to add-on resources in the backend, as this may lead to abnormal add-on behavior or unexpected issues. For example, parameter settings could be overwritten after an upgrade.
Add-on pods are prioritized over service pods. When cluster resources are limited, the add-on pods can use resources that would otherwise be allocated to service pods. This may result in the eviction of service pods.
Scheduling and Elasticity Add-ons¶
Add-on Name | Description |
|---|---|
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. | |
This add-on scales in or out the workload nodes in a cluster based on pod scheduling status and resource usage. | |
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. |
Cloud Native Observability Add-ons¶
Add-on Name | Description |
|---|---|
This add-on includes the Prometheus-operator and Prometheus components and provides easy-to-use, end-to-end Kubernetes cluster monitoring. | |
This add-on is developed based on Fluent Bit and OpenTelemetry for collecting logs. It supports CRD-based log collection policies, and collects and forwards standard output logs, container file logs, node logs, and Kubernetes events in a cluster. | |
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 is an aggregator for monitoring data of core cluster resources. | |
This add-on is an open-source visualized data monitoring platform. It provides you with various charts and panels for real-time monitoring, analysis, and visualization of various metrics and data sources. |
Cloud Native Heterogeneous Computing Add-ons¶
Add-on Name | Description |
|---|---|
This add-on supports and manages GPUs in containers. Only NVIDIA drivers are supported. |
Container Network Add-ons¶
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 provides application-layer forwarding functions, including load balancing, SSL proxies, and HTTP routing, for Services to support direct access from outside a cluster. | |
This add-on functions as a DaemonSet to run the DNS cache proxy on each cluster node to improve cluster DNS performance. |
Container Storage Add-ons¶
Add-on Name | Description |
|---|---|
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). |
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.