In Kubernetes, Services are used to expose application pods in order to decouple the front end from the back end. This allows you to use a loosely coupled microservices design. Services are classified into ClusterIP, NodePort, and LoadBalancer Services. This topic describes how to use LoadBalancer Services to expose applications in ACK Edge clusters.
Background information
Kubernetes clusters support all types of Services. For more information, see Service type.
You can create on-cloud node pools and edge node pools for ACK Edge clusters. Container Service for Kubernetes (ACK) clusters consist of on-cloud node pools and control planes hosted on the cloud.
In an ACK Edge cluster, you can create on-cloud node pools or edge node pools to use LoadBalancer Services to expose applications.
On-cloud node pools that use LoadBalancer Services
You can create LoadBalancer Services on the cloud and forward requests from hosts in virtual private cloud (VPCs) to workloads in data centers through Express Connect circuits.
The following table describes various solutions and provides links to the references.
Category | References |
Overview | |
SLB | |
CLB | |
NLB | |
Troubleshooting and FAQ |
ENS node pools that use LoadBalancer Services
You can connect computing resources in data centers residing in different network domains to the cloud. Each data center functions as a node pool. In addition, you can expose applications that belong to the same business across regions. This means that you can map a Service to multiple endpoints in data centers.
You can attach multiple VPCs with Edge Node Service (ENS) instances to an edge node in an ACK Edge cluster. Each VPC functions as a node pool, enabling the exposure of application pods across different VPCs. This configuration allows a Service to be accessed through multiple endpoints across various node pools.
ACK Edge clusters support only Edge Node Service (ENS) data centers and ENS load balancers.
ACK Edge clusters provide PoolServices to allow you to create custom cluster resources. The hosted component edge-controller-manager can automatically select a PoolService managed by a node pool based on the LoadBalancer Service you created. The lifecycle of Server Load Balancer (SLB) instances in the region of the PoolService is bound to the PoolService.
References
For more information about how to expose applications by using LoadBalancer Services, see Use ELB instances to expose Services in multiple regions.