Updated on 2024-01-24 GMT+08:00

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.

Table 1 Add-on list

Add-on Name

Introduction

coredns (System Resource Add-on, Mandatory)

CoreDNS is a DNS server that provides domain name resolution for Kubernetes clusters through chain plug-ins.

everest (System Resource Add-on, Mandatory)

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

npd

node-problem-detector (npd for short) 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.

dashboard

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.

autoscaler

The autoscaler add-on resizes a cluster based on pod scheduling status and resource usage.

metrics-server

metrics-server is an aggregator for monitoring data of core cluster resources.

cce-hpa-controller

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

Prometheus is an open-source system monitoring and alerting framework. CCE allows you to quickly install Prometheus as an add-on.

web-terminal

web-terminal is an add-on that 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.

gpu-beta

gpu-device-plugin is a device management add-on that supports GPUs in containers. It supports only NVIDIA drivers.

huawei-npu

huawei-npu is a management add-on for Huawei NPU devices in containers.

volcano

Volcano provides general-purpose, high-performance computing capabilities, 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

nginx-ingress provide application-layer forwarding functions, such as virtual hosts, load balancing, SSL proxy, and HTTP routing, for Services that can be directly accessed outside a cluster.

dew-provider

The dew-provider add-on is used to interconnect with , which allows you to mount secrets stored outside a cluster (that is, DEW for storing sensitive information) to pods. In this way, sensitive information can be decoupled from the cluster environment, preventing information leakage caused by program hardcoding or plaintext configuration.

dolphin

dolphin is a pod network monitoring add-on, which, in the current version, can be used to collect statistics about public network traffic of Kata containers in CCE Turbo clusters and common containers that use containerd as the runtime.

This add-on collects how many IPv4 packets and bytes are received and sent (including those sent to the public network). PodSelectors can be used to select monitoring backends to support multiple monitoring tasks and optional monitoring metrics. You can also obtain label information of pods. The monitoring information has been adapted to the Prometheus format. You can call the Prometheus API to view monitoring data.

node-local-dns

NodeLocal DNSCache improves cluster DNS performance by running DNS cache proxies as DaemonSets on cluster nodes.

kube-prometheus-stack

kube-prometheus-stack uses Prometheus-operator and Prometheus to provide easy-to-use, end-to-end Kubernetes cluster monitoring capabilities.

With this add-on, you can interconnect monitoring data with CIA to view monitoring data and configure alarms.

Add-on Lifecycle

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

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

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.

Related Operations

You can perform the operations described in Table 3 on the Add-ons page.
Table 3 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.