nav-img
Advanced

Overview

CCE provides multiple types of add-ons to extend cluster functions and meet feature requirements. You can install add-ons as required.

Notice

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 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 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 obtain pod labels. It 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.

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.

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 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.

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-on

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).

Container Security Add-ons

Add-on Name

Description

This 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.

Other Add-ons

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 users to manage applications running 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 the server.

Add-on Lifecycle

An add-on lifecycle involves all the statuses of the add-on from installation to uninstallation.

Table 1 Add-on statuses

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.

Related Operations

You can perform the operations listed in Table 2 on the Add-ons page.

Table 2 Related operations

Operation

Description

Procedure

Install

Install a specified add-on.

  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons.
  2. Click Install under the target add-on.

    Each add-on has different configuration parameters. For details, see the corresponding chapter.

  3. Click OK.

Upgrade

Upgrade an add-on to the new version.

  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons.
  2. If an add-on can be upgraded, the Upgrade button is displayed under it.

    Click Upgrade. Each add-on has different configuration parameters. For details, see the corresponding chapter.

  3. Click OK.

Edit

Edit add-on parameters.

  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons.
  2. Click Edit under the target add-on.

    Each add-on has different configuration parameters. For details, see the corresponding chapter.

  3. Click OK.

Uninstall

Uninstall an add-on from the cluster.

  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons.
  2. Click Uninstall under the target add-on.
  3. In the displayed dialog box, click Yes.

    This operation cannot be undone.

Roll back

Roll back an add-on to the source version.

NOTE:
  • This function is used to roll back an upgraded add-on to the source version, not to undo the editing of add-on parameters.
  • An add-on cannot be rolled back repeatedly.
  1. Log in to the CCE console and click the cluster name to access the cluster console. In the navigation pane, choose Add-ons.
  2. If an add-on can be rolled back, the Roll Back button is displayed under it.

    Click Roll Back.

  3. In the displayed dialog box, click Yes.
Note

Rollback is supported by the following add-ons of certain versions:

  • CoreDNS: 1.25.11 and later versions
  • CCE Container Storage (Everest): 2.1.19 and later versions
  • CCE Cluster 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
  • Volcano Scheduler: 1.11.4 and later versions
  • CCE Node Problem Detector: 1.18.22 and later versions