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: pkg/i2gw/implementations/kgateway/README.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,7 @@ The command should generate Gateway API and Kgateway resources.
61
61
-`nginx.ingress.kubernetes.io/proxy-read-timeout`
62
62
-`nginx.ingress.kubernetes.io/ssl-redirect`: When set to `"true"`, adds a `RequestRedirect` filter to HTTPRoute rules that redirects HTTP to HTTPS with a 301 status code.
63
63
-`nginx.ingress.kubernetes.io/force-ssl-redirect`: When set to `"true"`, adds a `RequestRedirect` filter to HTTPRoute rules that redirects HTTP to HTTPS with a 301 status code. Treated identically to `ssl-redirect`.
64
+
-`nginx.ingress.kubernetes.io/ssl-passthrough`: When set to `"true"`, enables TLS passthrough mode. Converts the Ingress to a `TLSRoute` with a Gateway listener using `protocol: TLS` and `tls.mode: Passthrough`. The HTTPRoute that would normally be created is removed.
64
65
65
66
### Backend Behavior
66
67
@@ -114,6 +115,7 @@ Examples:
114
115
- Rate limit annotations control `spec.rateLimit.local.tokenBucket`
115
116
- Timeout annotations control `spec.timeouts.request` or `streamIdle`
116
117
- SSL redirect annotations add `RequestRedirect` filters to HTTPRoute rules
118
+
- SSL passthrough annotation converts HTTPRoute to TLSRoute with TLS passthrough Gateway listener
117
119
118
120
## BackendConfigPolicy Projection
119
121
@@ -128,6 +130,19 @@ Currently supported:
128
130
If multiple Ingresses target the same Service with conflicting `proxy-connect-timeout` values,
129
131
the lowest timeout wins and a warning is emitted.
130
132
133
+
## TLSRoute Projection
134
+
135
+
Annotations that require TLS passthrough mode are converted into `TLSRoute` resources instead of `HTTPRoute` resources.
136
+
137
+
Currently supported:
138
+
139
+
-`nginx.ingress.kubernetes.io/ssl-passthrough`:
140
+
- When enabled, the Ingress is converted to a `TLSRoute` resource
141
+
- A Gateway listener is created with `protocol: TLS` and `tls.mode: Passthrough`
142
+
- The listener uses port 443 (when hostname is specified) or 8443 (default)
143
+
- The HTTPRoute that would normally be created is removed
144
+
- Backend services must handle TLS termination themselves
145
+
131
146
## Backend Projection
132
147
133
148
Annotations that change how upstreams are represented (rather than how they are load balanced or configured)
0 commit comments