Microservices Engine (MSE) cloud-native gateways are next-generation gateways compatible with Kubernetes Ingresses. Cloud-native gateways integrate the features of traditional traffic gateways and microservices gateways to provide benefits such as cost-effectiveness, security, high integrability, and high availability. Distributed Cloud Container Platform for Kubernetes (ACK One) uses a fully-managed MSE Ingress controller to manage MSE cloud-native gateways that serve as multi-cluster gateways. MSE cloud-native gateways can manage north-south traffic in multi-cluster deployments based on MSE Ingresses. This allows you to use features such as active zone-redundancy, multi-cluster load balancing, and header-based routing.
How it works
An MSE cloud-native gateway can centrally manage the north-south traffic of multiple Kubernetes clusters in the same region. For more information about MSE cloud-native gateways, see What is MSE? and Overview of cloud-native gateways.
An administrator can create an MSE cloud-native gateway by creating an
MseIngressConfigobject in an ACK One Fleet instance. The administrator can then connect associated clusters to the MSE cloud-native gateway.A developer can use
Ingresseson the ACK One Fleet instance to manage the traffic of multi-cluster applications. For example, the developer can use Ingresses to implement active zone-redundancy and traffic load balancing.
Limits
By default, a multi-cluster gateway can manage the traffic of multiple clusters deployed in the same virtual private cloud (VPC). To manage the traffic of multiple clusters deployed in different VPCs of a region, you need to use Cloud Enterprise Network (CEN) to connect the VPCs and ensure that their CIDR blocks do not overlap.
You cannot deploy multi-cluster gateways across regions.
Billing
For more information about the billing of multi-cluster gateways, see Billing overview.