Skip to content

Commit 20c2ff7

Browse files
committed
documentation
1 parent 7862bab commit 20c2ff7

File tree

2 files changed

+8
-16
lines changed

2 files changed

+8
-16
lines changed

docs/guide/gateway/l4gateway.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -174,19 +174,3 @@ spec:
174174
value: "60"
175175
```
176176

177-
### L4 Gateway API Limitations for NLBs
178-
The LBC implementation of the Gateway API for L4 routes, which provisions NLB, introduces specific constraints to align with NLB capabilities. These limitations are enforced during the reconciliation process and are critical for successful L4 traffic management.
179-
180-
#### Single Route Per L4 Gateway Listener:
181-
182-
**Limitation**: Each L4 Gateway Listener (configured via a Gateway resource for TCP, UDP, or TLS protocols) is designed to handle traffic for precisely one L4 Route resource (TCPRoute, UDPRoute, or TLSRoute). The controller does not support scenarios where multiple Route resources attempt to attach to the same L4 Gateway Listener and will throw a validation error during reconcile.
183-
184-
**Reasoning**: This constraint simplifies L4 listener rule management on NLBs, which primarily offer a default action for a given port/protocol.
185-
186-
#### Single Backend Reference Per L4 Route:
187-
188-
**Limitation**: Each L4 Route resource (TCPRoute, UDPRoute, or TLSRoute) must specify exactly one backend reference (backendRef). The controller explicitly disallows routes with zero or more than one backendRef throwing a validation error during reconcile
189-
190-
**Reasoning**: Unlike ALBs which support weighted target groups for traffic splitting across multiple backends, NLBs primarily forward traffic to a single target group for a given listener's default action. This aligns the LBC's L4 route translation with NLB's inherent capabilities, where weighted target groups are not a native feature for directly splitting traffic across multiple services on a single listener.
191-
192-
These validations ensure that the Kubernetes Gateway API definitions for L4 traffic can be correctly and unambiguously translated into the underlying AWS NLB constructs. Adhering to these limitations is essential for stable and predictable L4 load balancing behavior with the AWS Load Balancer Controller.

docs/guide/gateway/loadbalancerconfig.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -541,6 +541,14 @@ for a complete list.
541541

542542
**Default** Empty list
543543

544+
#### TargetGroupStickiness
545+
546+
`targetGroupStickiness`
547+
548+
An optional boolean that allows you to configure target group stickiness for weighted listeners on your Load Balancer.
549+
550+
**Default** null
551+
544552
### MutualAuthenticationAttributes
545553

546554
```

0 commit comments

Comments
 (0)