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
Copy file name to clipboardExpand all lines: geps/gep-1713/index.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -340,9 +340,9 @@ type ParentGatewayReference struct {
340
340
341
341
### YAML
342
342
343
-
The following example shows a `Gateway` with an HTTP listener and two child HTTPS `ListenerSets` with unique hostnames and certificates.
344
-
343
+
The following example shows a `Gateway` with an HTTP listener and two child HTTPS `ListenerSets` with unique hostnames and certificates.
345
344
Only `ListenerSets` from the same namespace of the `Gateway` will be accepted:
345
+
346
346
```yaml
347
347
apiVersion: gateway.networking.k8s.io/v1
348
348
kind: Gateway
@@ -439,8 +439,6 @@ spec:
439
439
440
440
Routes MUST be able to specify a `ListenerSet` as a `parentRef`. Routes can use `sectionName`/`port` fields in `ParentReference` to help target a specific listener. If no listener is targeted (`sectionName`/`port` are unset) then the Route attaches to all the listeners in the `ListenerSet`.
441
441
442
-
Routes MUST be able to attach to a `ListenerSet` and it's parent `Gateway` by having multiple `parentRefs` eg:
443
-
444
442
```yaml
445
443
apiVersion: gateway.networking.k8s.io/v1
446
444
kind: HTTPRoute
@@ -453,7 +451,8 @@ spec:
453
451
sectionName: second
454
452
```
455
453
456
-
To attach to listeners in both a `Gateway` and `ListenerSet` the route MUST have two `parentRefs`:
454
+
Routes MUST be able to attach to a `ListenerSet` and it's parent `Gateway` by having multiple `parentRefs` eg:
455
+
457
456
```yaml
458
457
apiVersion: gateway.networking.k8s.io/v1
459
458
kind: HTTPRoute
@@ -599,7 +598,7 @@ spec:
599
598
hostname: www.something.tld
600
599
protocol: HTTPS
601
600
port: 443
602
-
tls:
601
+
tls:
603
602
mode: Terminate
604
603
certificateRefs:
605
604
- kind: Secret
@@ -630,8 +629,9 @@ spec:
630
629
```
631
630
632
631
The ListenerSet `user-listenerset` should be marked as Conflicted, as the `parent-gateway`
633
-
have a listener definition called `foo` that conflicts with the ListenetSet definition
634
-
called `myapp`, as the following:
632
+
has a listener definition called `foo` that conflicts with the ListenetSet definition
633
+
called `myapp`. The conflict happens because hostname is the same on both `ListenerSet`
634
+
but they use different termination TLS certificates:
635
635
636
636
```yaml
637
637
apiVersion: gateway.networking.x-k8s.io/v1alpha1
@@ -646,7 +646,7 @@ status:
646
646
hostname: www.something.tld
647
647
protocol: HTTPS
648
648
port: 443
649
-
conditions:
649
+
conditions:
650
650
- message: ListenerSet has conflicts with Gateway 'infra/parent-gateway'
651
651
reason: Conflicted
652
652
status: "True"
@@ -729,8 +729,8 @@ status:
729
729
hostname: www.something.tld
730
730
protocol: HTTPS
731
731
port: 443
732
-
conditions:
733
-
- message: ListenerSet has conflicts with other listeners attached to the same Gateway
732
+
conditions:
733
+
- message: ListenerSet has conflicts with other listeners attached to the same Gateway
0 commit comments