Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe AWS Load Balancer Controller (LBC) watches Kubernetes networking resources and reconciles them into AWS load balancers. In Amazon EKS, an Ingress commonly provisions an Application Load Balancer (ALB) for HTTP and application traffic, while a Service of type LoadBalancer commonly provisions a Network Load Balancer (NLB) for network traffic. The controller configures those AWS resources; it is not itself the load balancer. These are AWS EKS mappings, not rules Kubernetes imposes on every cloud or controller.
How does the controller connect Kubernetes to AWS?
Kubernetes resources describe how an application should receive traffic. LBC observes selected resources, their class and annotations, then creates or updates corresponding Elastic Load Balancing resources in AWS. This reconciliation connects a cluster’s declared networking configuration to AWS infrastructure. See AWS’s AWS Load Balancer Controller overview.
As an Amazon Associate I earn from qualifying purchases.
The main distinction is traffic type: ALBs operate at Layer 7 and support application-level routing, while NLBs operate at Layer 4 for network traffic. The resource-to-load-balancer mapping below describes the EKS guidance for LBC; Kubernetes itself does not require these AWS products.
| Kubernetes resource | Typical result in AWS EKS guidance | Traffic and routing |
|---|---|---|
Ingress |
Application Load Balancer (ALB) | Layer 7 HTTP/application traffic; targets can be nodes or pod IPs, depending on target mode. |
Service with type: LoadBalancer |
Network Load Balancer (NLB) | Layer 4 network traffic; instance and IP target modes are documented. |
Gateway |
Application Load Balancer (ALB), with LBC version 2.14.0 or later | AWS says Gateway API standardizes more configuration than Ingress, which has often relied on controller-specific annotations. |
For the version-specific Gateway behavior and resource mapping, consult the EKS controller overview.
#1 Best Overall
How does traffic reach the pods?
Target mode determines whether a load balancer sends traffic through cluster nodes or directly to pod IP addresses. This affects routing and which environments the configuration can serve.
Instance targets: through a node and NodePort
In instance mode, the ALB registers cluster nodes as targets. It sends traffic to a Service NodePort on a node, and Kubernetes then routes the traffic to a pod. This is a node-mediated path.
IP targets: directly to pod addresses
In IP mode, the ALB registers pod IP addresses and sends traffic directly to the pods. AWS requires IP targets for ALBs serving pods on Fargate or EKS Hybrid Nodes. For hybrid workloads, pod IP addresses also need to be routable from AWS. NLBs support instance or IP targets as well, subject to the relevant service and environment requirements. AWS documents these modes in its ALB guidance and NLB guidance.
Which load-balancing path fits the traffic?
Choose based on the protocol, target destination, workload environment and required configuration—not simply on whether the application runs in Kubernetes.
- HTTP or application-level routing: Use the Ingress-to-ALB path when the workload needs Layer 7 application traffic handling.
- TCP or UDP network traffic: A LoadBalancer Service with an NLB is the documented EKS path for Layer 4 traffic.
- Fargate or EKS Hybrid Nodes behind an ALB: Use IP targets; for hybrid nodes, verify that the pod IPs are reachable from AWS.
- Exposure and placement: Decide whether the endpoint should be internal or internet-facing and ensure subnet selection fits that purpose. AWS says NLBs default to an internal scheme; making one internet-facing requires the corresponding annotation.
- Configuration compatibility: Check that the annotations and settings you need are supported by the provisioning mode you choose.
For ALB configuration, target behavior and related security guidance, use AWS’s application and HTTP traffic guide. For NLB exposure and Service annotations, see its TCP and UDP traffic guide.
What do annotations and resource settings control?
Kubernetes resources are the configuration surface: the resource type and class identify the intended handling, while annotations can shape the AWS load balancer that is provisioned. Depending on the resource and controller behavior, settings can affect subnet selection, internal or internet-facing scheme, target type, health checks and security configuration.
Rank #3
Do not assume an annotation is universal across controllers or EKS operating modes. Check the current AWS documentation for the precise annotation key, accepted value and compatibility for the resource you are configuring. AWS provides examples and supported settings in its ALB Ingress guide and NLB guide.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Do you need to install LBC on EKS Auto Mode?
Not for Auto Mode’s documented NLB provisioning of LoadBalancer Services: EKS Auto Mode provisions and configures those NLBs without a separate LBC installation. However, Auto Mode does not support every Service annotation available in LBC. Compare the required settings with the Auto Mode NLB annotation guidance before choosing that route.
For other EKS configurations, AWS describes LBC as an optional networking add-on and recommends it for provisioning NLBs rather than relying on the legacy Kubernetes cloud provider controller. That legacy path can provision Classic Load Balancers; consult AWS’s networking add-ons guidance before a new deployment or migration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What does installation and operation involve?
LBC needs an existing EKS cluster, AWS permissions to manage load-balancer resources, and suitable cluster networking prerequisites. Installation is therefore an infrastructure and IAM task, not just applying a Kubernetes object. AWS recommends Helm for users new to EKS and also documents manifest installation for advanced configurations, including restricted access to public container registries.
AWS’s manifest installation guide covers prerequisites, IAM configuration, controller installation and verification. With IAM Roles for Service Accounts (IRSA), the OIDC provider ARN in the trust policy is specific to the cluster. Use AWS’s current policy and commands rather than copying stale installation instructions, since implementation steps and version compatibility can change.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesUnderstand the Service mutating webhook
AWS says LBC versions 2.5 and newer use a mutating webhook by default to set spec.loadBalancerClass to service.k8s.aws/nlb for new LoadBalancer Services. The behavior can be disabled with the Helm chart value enableServiceMutatorWebhook: false. This does not mean existing Classic Load Balancers are changed; AWS says existing ones continue to work. Details are in the controller overview.
Best Value
What version and migration details matter?
LBC version 2.14.0 or later creates an ALB when a Kubernetes Gateway is created, according to AWS. If you plan to use Gateway API resources, check that your deployed controller version supports this behavior.
AWS identifies the AWS ALB Ingress Controller and 0.1.x versions of AWS Load Balancer Controller as deprecated. AWS says deprecated versions cannot be upgraded and must be removed before installing a current controller. Check the current release-specific AWS instructions for exact compatibility and migration steps; the live documentation may change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
