Skip to content

Commit e75ed3b

Browse files
author
Ryan Lymburner
authored
Merge branch 'aws:main' into fix-tlsroute-hostname-validation
2 parents a94404d + f5ff454 commit e75ed3b

File tree

8 files changed

+3260
-7968
lines changed

8 files changed

+3260
-7968
lines changed

config/manager/kustomization.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@ configMapGenerator:
1313
images:
1414
- name: controller
1515
newName: public.ecr.aws/aws-application-networking-k8s/aws-gateway-controller
16-
newTag: v1.1.0
16+
newTag: v1.1.1

docs/guides/advanced-configurations.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,38 @@ However, the controller utilizes [IMDS](https://docs.aws.amazon.com/AWSEC2/lates
1616

1717
- **If your cluster cannot access to IMDS.** ensure to specify the[configuration variables](environment.md) when installing the controller.
1818

19+
### Rule Priority Configuration
20+
21+
You can manually assign priorities to rules using the custom annotation `application-networking.k8s.aws/rule-{index}-priority`. This annotation allows you to explicitly set the priority for specific rules in your route configurations.
22+
23+
For example, to set priorities for multiple rules in an HTTPRoute:
24+
25+
```yaml
26+
apiVersion: gateway.networking.k8s.io/v1beta1
27+
kind: HTTPRoute
28+
metadata:
29+
name: example-route
30+
annotations:
31+
application-networking.k8s.aws/rule-0-priority: "200" # First rule gets higher priority
32+
application-networking.k8s.aws/rule-1-priority: "100" # Second rule gets lower priority
33+
spec:
34+
rules:
35+
- matches: # This is rule[0]
36+
- path:
37+
type: PathPrefix
38+
value: /api/v2
39+
- matches: # This is rule[1]
40+
- path:
41+
type: PathPrefix
42+
value: /api
43+
```
44+
45+
The `{index}` in the annotation corresponds to the zero-based index of the rule in the rules array. In this example:
46+
- `rule-0-priority: "200"` applies to the first rule matching `/api/v2`
47+
- `rule-1-priority: "100"` applies to the second rule matching `/api`
48+
49+
Higher priority values indicate higher precedence, so requests to `/api/v2` will be matched by the first rule (priority 200) before the second rule (priority 100) is considered.
50+
1951
### IPv6 support
2052

2153
IPv6 address type is automatically used for your services and pods if

0 commit comments

Comments
 (0)