Google Distributed Cloud (GDC) air-gapped provides load balancers that enable applications to expose services to one another. Load balancers allocate a stable virtual IP (VIP) address that balances traffic over a set of backend workloads. Load balancers in GDC perform layer four (L4) load balancing, which means they map a set of configured frontend TCP or UDP ports to corresponding backend ports.
Load balancers are configured for containerized workloads using the Kubernetes
Service API. This section describes how to configure load-balancing Service
objects in user clusters. For more information about Kubernetes Services, see
https://kubernetes.io/docs/concepts/services-networking/service/
GDC applications have access to the following networking service types:
- Internal Load Balancer (ILB): lets you expose a service to other clusters within the organization.
- External Load Balancer (ELB): allocates a VIP address from a range that is routable from external workloads and exposes services outside of the GDC organization, such as other organizations inside or outside of the GDC instance.
Load balancers are configured in a project and can only select backend workloads in that project. Both Internal and External load balancers currently support selecting backend workloads from a single cluster only.
Service virtual IP addresses
ILBs allocate VIP addresses that are internal only to the organization. These VIP addresses are not reachable from outside the organization; therefore, you can only use them to expose services to other applications within an organization. These IP addresses may overlap between organizations in the same instance.
On the other hand, ELBs allocate VIP addresses that are externally reachable from outside the organization. For this reason, ELB VIP addresses must be unique among all organizations. Typically, fewer ELB VIP addresses will be available for use by the organization.