NLB

Health Checks

Network Load Balancers use active and passive health checks to determine whether a target is available to handle requests.

By default, each load balancer node routes requests only to the healthy targets in its Availability Zone. If you enable cross-zone load balancing, each load balancer node routes requests to the healthy targets in all enabled Availability Zones.

Types: - Active - Passive

Common CLI actions

Get public NLB DNS for kube-apiserver on OpenShift cluster

CLUSTER_NAME=$(oc get infrastructure cluster -o jsonpath="{.status.infrastructureName}")

NLB_NAME="${CLUSTER_NAME}-ext"

KAS_NLB_EXT_DNS="$(aws elbv2 describe-load-balancers |jq -r ".LoadBalancers[] | select(.LoadBalancerName==\"${NLB_NAME}\").DNSName")"

References:

• AWS-Docs/What is a Network Load Balancer?
• AWS-Docs/NLB Troubleshooting
• AWS-Blog/Avoiding overload in distributed systems by putting the smaller service in control
• Article/HyperPlane: A Scalable Low-Latency Notification Accelerator for Software Data Planes
• Article/Hyperplane partitioning: An approach to global data partitioning for distributed memory machines
• Article-PDF/Hyperplane partitioning: An approach to global data partitioning for distributed memory machines
• Sandbox application to use different servers for Service and Health Check