ACK Edge provides various types of components. You can install, upgrade, or uninstall components based on your business requirements. The topic describes the cluster components that are managed by ACK Edge based on their features.
Prerequisites
An ACK Edge cluster is created. For more information, see Create an ACK Edge cluster.
Component management
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose .
On the Add-ons page, find the component that you want to manage and install, uninstall, or update the component or modify the control plane parameters of the component.
Component types
The cluster components managed by Container Service for Kubernetes (ACK) are classified into system components and optional components.
System components are automatically installed when you create an ACK Edge cluster. System components cannot be uninstalled. You can update system components at the earliest opportunity.
Optional components extend the features of clusters. You can install optional components when you create an ACK Edge cluster. You can install or uninstall components, or update configurations based on your business requirements. Update optional components at the earliest opportunity.
Key components
Name | Type | Description |
System component | Serves as the access gateway to a Kubernetes cluster. | |
System component | Manages the resources in a Kubernetes cluster. | |
System component | Schedules pods to nodes that meet resource usage and pod scheduling requirements. | |
System component | Enables integration between Kubernetes and Alibaba Cloud basic services, such as Classic Load Balancer (CLB) and Virtual Private Cloud (VPC). | |
System component | Provides the node lifecycle management feature. | |
System component | Connects to Alibaba Cloud edge products, such as Edge Load Balancer (ELB). | |
System component | The yurt-app-manager component provides cell-based management at the edge for ACK Edge clusters, such as nodepool and yurtappset. | |
System component | The proxy for traffic distribution between the components that are deployed on edge nodes and the kube-apiserver component that is deployed in the cloud. This component can run in Edge mode or Cloud mode. |
Application management components
Name | Type | Description |
Optional component | Provides image distribution and allows you to manage application containers and sidecar containers in an efficient manner. | |
Optional component | This component is developed based on the open source Velero project and allows you to migrate Kubernetes applications. |
Logs and monitoring components
Name | Type | Description |
System component | Enables integration with CloudMonitor. | |
System component | This component is developed based on the open source component Metrics Server and can collect resource metrics. This component also provides the Metrics API for data consumption and supports Horizontal Pod Autoscaler (HPA). | |
Optional component | This component is developed based on the open source component Node Problem Detector (NPD), and can monitor the health of nodes and connect to third-party monitoring platforms. | |
Optional component | Collects container logs by using Simple Log Service. | |
Optional component | Integrates with Application Real-Time Monitoring Service (ARMS) and Microservices Engine (MSE). ack-onepilot allows you to enable ARMS and MSE for Java or Golang applications in your ACK cluster. | |
Optional component | Allows Alibaba Cloud Genomics Service (AGS) users to monitor the resources that are used by each node in AGS workflows. | |
Optional component | Monitors ACK clusters by using Managed Service for Prometheus. | |
Optional component | ack-arms-cmonitor is a monitoring component provided by the ARMS extended Berkeley Packet Filter (eBPF) edition for ACK clusters. |
Storage components
Name | Type | Description |
Optional component | Allows you to mount and unmount volumes. This component is automatically installed if you select the Container Storage Interface (CSI) plug-in when you create ACK clusters. | |
Optional component | Allows you to automate volume provisioning. This component is automatically installed if you select the CSI plug-in when you create ACK clusters. | |
Optional component | Manages the lifecycle of storage components. | |
Optional component | Automates the management of computing and storage resources of nodes, and allows you to manage storage resources by using LVM. |
Networking components
Name | Type | Description |
System component | The default component that is used to implement DNS-based service discovery in ACK clusters. This component follows the specifications of DNS-based service discovery in Kubernetes. | |
System component | A Container Network Interface (CNI) plug-in that allows you to create a virtual network for containers based on VPC. This component is automatically installed if you select the Flannel plug-in when you create ACK clusters. | |
System component | Terway Edge is used as a CNI plug-in to create an underlay network for communication in ACK Edge clusters. | |
Optional component | The Application Load Balancer (ALB) Ingress controller is compatible with NGINX Ingresses and provides powerful traffic management capabilities based on ALB instances. The ALB Ingress controller supports complex routing, automatic certificate discovery, and the HTTP, HTTPS, and Quick UDP Internet Connection (QUIC) protocols. These features meet the requirements of cloud-native applications for ultra-high elasticity and balancing of heavy traffic loads at Layer 7. Pods can be deployed only in on-cloud node pools in ACK Edge. |
Security components
Name | Type | Description |
System component | Allows you to pull private images without passwords from instances of Container Registry Enterprise Edition and Personal Edition. | |
Optional component | Helps you manage and use the policies executed by Open Policy Agent (OPA) in ACK clusters and allows you to manage the labels of namespaces. | |
Optional component | A key component that is used to perform security inspections. | |
Optional component | A key component that is used to manage pod security policies. |
Auto scaling
Name | Type | Description |
Optional component | This component is used to enable resource scaling by schedule. |
Other components
Name | Type | Description |
Optional component | A key component that is used by ACK to support service level objective (SLO)-aware workload scheduling. This component improves resource utilization and ensures the performance of your applications. | |
Optional component | The component that provide the on-demand image loading feature. | |
Optional component | The cross-region O&M communication component. | |
edge-tunnel (replaced with Raven in 1.26) | Optional component | A component that establishes reverse tunnels, which are commonly used to enable communication between different networks. |