You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IngressGroup feature enables you to group multiple Ingress resources together.
@@ -104,7 +105,7 @@ By default, Ingresses don't belong to any IngressGroup, and we treat it as a "im
104
105
other Kubernetes users may create/modify their Ingresses to belong to the same IngressGroup, and can thus add more rules or overwrite existing rules with higher priority to the ALB for your Ingress.
105
106
106
107
We'll add more fine-grained access-control in future versions.
107
-
108
+
108
109
!!!note "Rename behavior"
109
110
The ALB for an IngressGroup is found by searching for an AWS tag `ingress.k8s.aws/stack` tag with the name of the IngressGroup as its value. For an implicit IngressGroup, the value is `namespace/ingressname`.
110
111
@@ -195,9 +196,9 @@ Traffic Routing can be controlled with following annotations:
195
196
- Once defined on a single Ingress, it impacts every Ingress within the IngressGroup.
196
197
197
198
!!!note "Annotation Behavior"
198
-
199
+
199
200
- This annotation **takes effect only during the creation** of the Ingress. If the Ingress already exists, the change will not be applied until the Ingress is **deleted and recreated**.
@@ -499,9 +500,9 @@ Traffic Routing can be controlled with following annotations:
499
500
name: use-annotation
500
501
```
501
502
502
-
!!!note
503
+
!!!note
503
504
If you are using `alb.ingress.kubernetes.io/target-group-attributes` with `stickiness.enabled=true`, you should add `TargetGroupStickinessConfig` under `alb.ingress.kubernetes.io/actions.weighted-routing`
504
-
505
+
505
506
!!!example
506
507
507
508
```yaml
@@ -843,10 +844,10 @@ TLS support can be controlled with the following annotations:
843
844
844
845
- <aname="mutual-authentication">`alb.ingress.kubernetes.io/mutual-authentication`</a> specifies the mutual authentication configuration that should be assigned to the Application Load Balancer secure listener ports. See [Mutual authentication with TLS](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html) in the AWS documentation for more details.
845
846
846
-
!!!note
847
+
!!!note
847
848
- This annotation is not applicable for Outposts, Local Zones or Wavelength zones.
848
849
- "Configuration Options"
849
-
- `port: listen port `
850
+
- `port: listen port `
850
851
- Must be an HTTPS port specified by [listen-ports](#listen-ports).
@@ -1077,11 +1078,11 @@ Load balancer capacity unit reservation can be configured via following annotati
1077
1078
## Enable frontend NLB
1078
1079
When this option is set to true, the controller will automatically provision a Network Load Balancer and register the Application Load Balancer as its target. Additional annotations are available to customize the NLB configurations, including options for scheme, security groups, subnets, and health check. The ingress resource will have two status entries, one for the NLB DNS and one for the ALB DNS. This allows users to combine the benefits of NLB and ALB into a single solution, leveraging NLB features like static IP address and PrivateLink, while retaining the rich routing capabilities of ALB.
1079
1080
1080
-
!!!warning
1081
+
!!!warning
1081
1082
- If you need to change the ALB [scheme](#scheme), make sure to disable this feature first. Changing the scheme will create a new ALB, which could interfere with the current configuration.
1082
1083
- If you create ingress and enable the feature at once, provisioning the NLB and registering the ALB as target can take up to 3-4 mins to complete.
- <a name="frontend-nlb-tags">`alb.ingress.kubernetes.io/frontend-nlb-tags`</a> specifies additional tags to be applied to the frontend NLB. If not specified, the tags from ALB (specified via `alb.ingress.kubernetes.io/tags`) will be propagated to the NLB.
1193
+
1194
+
!!!note "Merge Behavior"
1195
+
`frontend-nlb-tags` is exclusive across all Ingresses in IngressGroup.
1196
+
If specified on multiple Ingresses within IngressGroup, the values must match.
0 commit comments