Both Container Service for Kubernetes (ACK) clusters and serverless Kubernetes (ASK) clusters support NGINX Ingresses andApplication Load Balancer (ALB) Ingresses. ALB Ingresses are fully managed by Alibaba Cloud, while NGINX Ingresses require manual maintenance. This topic describes the differences between NGINX Ingresses and ALB Ingresses from multiple perspectives.
The NGINX Ingress component requires manual maintenance. If you want to customize gateways, you can choose NGINX Ingresses. ALB Ingresses are implemented based on ALB instances. ALB Ingresses support auto scaling and are fully managed by Alibaba Cloud. An ALB instance supports one million queries per second (QPS), which provides ALB Ingresses with improved traffic routing capabilities. The following table describes the scenarios of NGINX Ingresses and ALB Ingresses.
Item | Scenario |
---|---|
Nginx Ingress |
|
ALB Ingress |
|
The following table describes the differences between NGINX Ingresses and ALB Ingresses.
Item | Nginx Ingress | ALB Ingress |
---|---|---|
Service positioning |
|
|
Architecture | Provides extended features based on NGINX and Lua. |
|
Basic routing |
|
|
Protocol | HTTP and HTTPS are supported. |
|
Configuration change |
|
Allows you to change the configuration by calling API operations. This method is more efficient than using the list-watch mechanism to modify the configuration. |
Authentication |
|
Supports TLS-based authentication. |
Performance |
|
|
Observability |
|
|
O&M |
|
|
Security |
|
|
Service governance |
|
|
Extended features | Supports Lua for configuring extended features. | Supports AScript for configuring extended features. For more information, see Overview of AScript. |
Cloud-native support |
|
|