Skip to content

Commit b924830

Browse files
authored
Merge pull request #584 from dumlutimuralp/patch-1
Update loadbalancing.md
2 parents 9ce5013 + 529b409 commit b924830

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

content/networking/loadbalancing/loadbalancing.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,6 @@ When deployed in an EKS Cluster the [AWS Load Balancer controller](https://docs.
77
create and manage AWS Elastic Load Balancers for that cluster.
88
When a Kubernetes Service of type LoadBalancer is created, the AWS Load Balancer controller creates a [Network Load Balancer (NLB)](https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html) which load balances received traffic at Layer 4 of the OSI model. While when a Kubernetes Ingress object is created, the AWS Load Balancer Controller creates an [Application Load Balancer (ALB)](https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html) which load balances traffic at Layer 7 of the OSI model.
99

10-
11-
# Recommendations
12-
13-
1410
## Choosing Load Balancer Type
1511

1612
The AWS Elastic Load Balancing portfolio supports the following load balancers: Application Load Balancers (ALB), Network Load Balancers (NLB), Gateway Load Balancers (GWLB), and Classic Load Balancers (CLB). This best practices section will focus on the ALB and NLB which are the two which are most relevant for EKS Clusters.

0 commit comments

Comments
 (0)