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 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.
Add-on Name | Description |
|---|---|
This add-on provides general computing capabilities such as a high-performance task scheduling engine, heterogeneous chip management, and task operation management, serving 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. | |
This add-on automatically adjusts the CPU and memory resource requests for pods based on their historical resource usage. |
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 based on the policies you configured. | |
This add-on monitors abnormal events of cluster nodes and connects with 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 monitors and manages container network traffic. It collects how many IPv4 packets and bytes are received and sent (including those sent to the Internet) and allows you to select the monitoring backends using PodSelector. It supports multiple monitoring tasks, allows you to select monitoring metrics, and allows you to obtain pod labels. The monitoring information has been adapted to Prometheus. You can call the Prometheus API to view monitoring data. | |
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. | |
This add-on is an open-source system monitoring and alerting framework. CCE allows you to quickly install Prometheus as an add-on. |
Add-on Name | Description |
|---|---|
This add-on supports and manages GPUs in containers. Only NVIDIA drivers are supported. |
Add-on Name | Description |
|---|---|
This add-on is a DNS server that provides domain name resolution for Kubernetes clusters through chained plugins.. | |
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. |
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 Name | Description |
|---|---|
This add-on interconnects with Data Encryption Workshop (DEW). It allows you to mount secrets stored outside a cluster (DEW for storing sensitive information) to service pods. In this way, sensitive information can be decoupled from the cluster environment, which prevents information leakage caused by program hardcoding or plaintext configuration. |
Add-on Name | Description |
|---|---|
This add-on is a general-purpose, web-based UI for Kubernetes clusters and integrates all commands that can be used in the command-line interface (CLI). It allows you to manage applications in a cluster and troubleshoot faults, as well as manage the cluster itself. | |
This add-on is a Kubernetes-based extension suite that automates cloud native application tasks like deployment, release, O&M, and availability protection. | |
This add-on is a customizable cloud native policy controller based on Open Policy Agent (OPA). It helps enhance policy execution and governance and provides more security policy rules that comply with Kubernetes application scenarios in clusters. | |
This add-on allows you to use kubectl on a web UI. It can connect to Linux by using WebSocket through a browser and provides APIs for integration into independent systems. It can be directly used as a service to obtain information through the configuration management database (CMDB) and log in to servers. |
An add-on lifecycle involves all the statuses from installation to uninstallation.
Status | Attribute | Description |
|---|---|---|
Running | Stable state | The add-on is running properly, all add-on pods 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 pods 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 pods are not properly deployed. |
Installing | Intermediate state | The add-on is being deployed. If all pods 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 | The add-on installation failed. Uninstall it and try again. |
Upgrading | Intermediate state | The add-on is being upgraded. |
Upgrade failed | Stable state | The add-on upgrade failed. Upgrade it again, or uninstall it and try again. |
Rolling back | Intermediate state | The add-on is being rolled 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 | The add-on deletion failed. Try again. |
Unknown | Stable state | The add-on release is not 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 is in the Unknown state and "don't install the addon in this cluster" is returned in status.Reason, this issue is typically caused by the deletion of the secret associated with the Helm release of the add-on by mistake. In this case, uninstall the add-on and reinstall it with the same configurations.
You can perform the operations listed in Table 2 on the Add-ons page.
Operation | Description | Procedure |
|---|---|---|
Installing the add-on | Install a specified add-on. |
|
Upgrading the add-on | Upgrade an add-on to the new version. |
|
Editing the add-on | Edit add-on parameters. |
|
Uninstalling the add-on | Uninstall an add-on from the cluster. |
|
Rolling back the add-on | Roll back an add-on to the source version. NOTE:
|
|
Rollback is supported by the following add-ons of certain versions: