feat: set OverlappingTLSConfig condition for HTTPS listeners with conflicting hostnames or certs#5777
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5777 +/- ##
==========================================
+ Coverage 65.32% 65.37% +0.04%
==========================================
Files 222 222
Lines 35459 35611 +152
==========================================
+ Hits 23164 23281 +117
- Misses 10859 10886 +27
- Partials 1436 1444 +8 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
881cb50 to
78b68a7
Compare
4fd6960 to
c632b88
Compare
c632b88 to
c88d616
Compare
Signed-off-by: Huabing (Robin) Zhao <zhaohuabing@gmail.com>
c88d616 to
e95749f
Compare
Signed-off-by: Huabing (Robin) Zhao <zhaohuabing@gmail.com>
| } | ||
|
|
||
| // isOverlappingHostname checks if two hostnames overlap. | ||
| func isOverlappingHostname(hostname1, hostname2 *gwapiv1.Hostname) bool { |
There was a problem hiding this comment.
can we reuse / dedup some of
gateway/internal/gatewayapi/route.go
Line 820 in 7b64768
There was a problem hiding this comment.
I don't think we can. These are handling two different logics.
Signed-off-by: Huabing (Robin) Zhao <zhaohuabing@gmail.com>
|
Do we treat merge gateway correctly here and consider overlap across merged GWs? If not, we can do that as a further improvement. |
Signed-off-by: Huabing (Robin) Zhao <zhaohuabing@gmail.com>
Track this separately here as we're trying to release v1.4 rc today. #5860 |
This PR adds support for
OverlappingTLSConfigcondition in GatewayStatus. This condition is set if there are overlapping hostnames or certificates between listeners. The ALPN protocol is set to HTTP/1.1 for the overlapping listeners to avoid HTTP/2 Connection Coalescing.Implements: #5598
Part of: #2675
Release Notes: Yes
Reference: https://gateway-api.sigs.k8s.io/geps/gep-3567/