OSDOCS-16473 Ingress controller route timeout configurable variables …#106920
OSDOCS-16473 Ingress controller route timeout configurable variables …#106920jmanthei wants to merge 1 commit intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
size/M
jmanthei
force-pushed
the
OSDOCS-16374
branch
from
ecad97f to
7ccfa3a
Compare
jmanthei
force-pushed
the
OSDOCS-16374
branch
3 times, most recently
from
e049e62 to
b308dc1
Compare
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.TaskContents: The '.Procedure' block title is missing.
| [role="_abstract"] | ||
| To manage connection durations and optimize performance of your Ingress Controller, you can configure router timeout variables. These variables control how long the router waits for client responses, server data, or established connections before closing them. | ||
|
|
||
| .Configuring a router timeout |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.TaskTitle: Unsupported titles cannot be mapped to DITA tasks.
| [role="_abstract"] | ||
| To manage connection durations and optimize performance of your Ingress Controller, you can configure router timeout variables. These variables control how long the router waits for client responses, server data, or established connections before closing them. | ||
|
|
||
| .Configuring a router timeout |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.BlockTitle: Block titles can only be assigned to examples, figures, and tables in DITA.
|
|
||
| |=== | ||
|
|
||
| .A route setting custom timeout |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.TaskTitle: Unsupported titles cannot be mapped to DITA tasks.
| haproxy.router.openshift.io/timeout: 5500ms <1> | ||
| ... | ||
| ---- | ||
| <1> Specifies the new timeout with HAProxy supported units (`us`, `ms`, `s`, `m`, `h`, `d`). If the unit is not provided, `ms` is the default. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.CalloutList: Callouts are not supported in DITA.
jmanthei
force-pushed
the
OSDOCS-16374
branch
from
ed9feef to
e301de5
Compare
|
Passes asciiditavale check - one block title warning - fixing |
…table placed in correct section
jmanthei
force-pushed
the
OSDOCS-16374
branch
from
352fee7 to
05f3b59
Compare
|
@jmanthei: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
All clear for asciiditavale checks |
melvinjoseph86
left a comment
melvinjoseph86
left a comment
There was a problem hiding this comment.
@jmanthei is PR commit message with OSDOCS-16473 is the intended one for https://issues.redhat.com/browse/OSDOCS-16374?
| | `ROUTER_DEFAULT_SERVER_TIMEOUT` | `30s` | Length of time that a server has to acknowledge or send data. | ||
| | `ROUTER_DEFAULT_TUNNEL_TIMEOUT` | `1h` | Length of time for TCP or WebSocket connections to remain open. This timeout period resets whenever HAProxy reloads. |
There was a problem hiding this comment.
these two belongs to https://issues.redhat.com/browse/OSDOCS-16375
| ==Example of a route setting custom timeout | ||
| [source,yaml] | ||
| ---- | ||
| apiVersion: route.openshift.io/v1 | ||
| kind: Route | ||
| metadata: | ||
| annotations: | ||
| haproxy.router.openshift.io/timeout: 5500ms | ||
| ... | ||
| ---- | ||
|
|
||
| [NOTE] | ||
| ==== | ||
| Setting a server-side timeout value for passthrough routes too low can cause | ||
| WebSocket connections to timeout frequently on that route. | ||
| ==== No newline at end of file |
There was a problem hiding this comment.
these part also belongs to https://issues.redhat.com/browse/OSDOCS-16375
4 participants
…table placed in correct section
Version(s): 4.12+
Issue: https://issues.redhat.com/browse/OSDOCS-16374
Link to docs preview:
QE review:
Additional information: