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: docs-web/configuration/transportserver-resource.md
+45-2Lines changed: 45 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,7 @@ This document is the reference documentation for the TransportServer resource. T
15
15
-[Listener](#listener)
16
16
-[Upstream](#upstream)
17
17
-[UpstreamParameters](#upstreamparameters)
18
+
-[SessionParameters](#sessionparameters)
18
19
-[Action](#action)
19
20
-[Using TransportServer](#using-transportserver)
20
21
-[Validation](#validation)
@@ -182,11 +183,15 @@ port: 8443
182
183
183
184
### UpstreamParameters
184
185
185
-
The upstream parameters define various parameters for the upstreams. For now, only UDP-related parameters are supported:
186
+
The upstream parameters define various parameters for the upstreams:
186
187
```yaml
187
188
upstreamParameters:
188
189
udpRequests: 1
189
190
udpResponses: 1
191
+
connectTimeout: 60s
192
+
nextUpstream: true
193
+
nextUpstreamTimeout: 50s
194
+
nextUpstreamTries: 1
190
195
```
191
196
192
197
```eval_rst
@@ -205,6 +210,44 @@ upstreamParameters:
205
210
- The number of datagrams expected from the proxied server in response to a client datagram. See the `proxy_responses <https://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_responses>`_ directive. By default, the number of datagrams is not limited.
206
211
- ``int``
207
212
- No
213
+
* - ``connectTimeout``
214
+
- The timeout for establishing a connection with a proxied server. See the `proxy_connect_timeout <http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_connect_timeout>`_ directive. The default is ``60s``.
215
+
- ``string``
216
+
- No
217
+
* - ``nextUpstream``
218
+
- If a connection to the proxied server cannot be established, determines whether a client connection will be passed to the next server. See the `proxy_next_upstream <http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_next_upstream>`_ directive. The default is ``true``.
219
+
- bool
220
+
- No
221
+
* - ``nextUpstreamTries``
222
+
- The number of tries for passing a connection to the next server. See the `proxy_next_upstream_tries <http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_next_upstream_tries>`_ directive. The default is ``0``.
223
+
- ``int``
224
+
- No
225
+
* - ``nextUpstreamTimeout``
226
+
- The time allowed to pass a connection to the next server. See the `proxy_next_upstream_timeout <http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_next_upstream_timeout>`_ directive. The default us ``0``.
227
+
- ``string``
228
+
- No
229
+
```
230
+
231
+
### SessionParameters
232
+
233
+
The session parameters define various parameters for TCP connections and UDP sessions.
234
+
```yaml
235
+
sessionParameters:
236
+
timeout: 50s
237
+
```
238
+
239
+
```eval_rst
240
+
.. list-table::
241
+
:header-rows: 1
242
+
243
+
* - Field
244
+
- Description
245
+
- Type
246
+
- Required
247
+
* - ``timeout``
248
+
- The timeout between two succesive read or write operations on client or proxied server connections. See `proxy_timeout <http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html#proxy_timeout>`_ directive. The default is ``10m``.
249
+
- ``string``
250
+
- No
208
251
```
209
252
210
253
### Action
@@ -312,4 +355,4 @@ The [ConfigMap](/nginx-ingress-controller/configuration/global-configuration/con
312
355
As of Release 1.7, the TransportServer resource is a preview feature. Currently, it comes with the following limitations:
313
356
* When using TLS Passthrough, it is not possible to configure [Proxy Protocol](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/proxy-protocol) for port 443 both for regular HTTPS and TLS Passthrough traffic.
314
357
* If multiple TCP (or UDP) TransportServers reference the same listener, only one of them will receive the traffic. Moreover, until there is only one TransportServer, NGINX will fail to reload. If this happens, the IC will report a warning event with the `AddedOrUpdatedWithError` reason for the resource, which caused the problem, and also report the error in the logs.
315
-
* If multiple TLS Passthrough TransportServers have the same hostname, only one of them will receive the traffic. If this happens, the IC will report a warning in the logs like `host "app.example.com" is used by more than one TransportServers`.
358
+
* If multiple TLS Passthrough TransportServers have the same hostname, only one of them will receive the traffic. If this happens, the IC will report a warning in the logs like `host "app.example.com" is used by more than one TransportServers`.
0 commit comments