Automator: update istio.io@ reference docs (#14348)

This commit is contained in:
Istio Automation 2023-12-15 18:12:36 -08:00 committed by GitHub
parent 0837b626e3
commit da5d6b9c84
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 36 additions and 0 deletions

View File

@ -1749,6 +1749,24 @@ No
was established. If not set, there is no max duration. When max_connection_duration
is reached the connection will be closed. Duration must be at least 1ms.</p>
</td>
<td>
No
</td>
</tr>
<tr id="ConnectionPoolSettings-TCPSettings-idle_timeout">
<td><code>idleTimeout</code></td>
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">Duration</a></code></td>
<td>
<p>The idle timeout for TCP connections.
The idle timeout is defined as the period in which there are no bytes sent or received on either
the upstream or downstream connection.
If not set, the default idle timeout is 1 hour. If set to 0s, the timeout will be disabled.
Idle timeout is not configured per each cluster individually when weighted destinations are used,
because idleTimeout is a property of a listener, not a cluster. In that case, idleTimeout
specified in a destination rule for the first weighted route is configured in the listener,
which means also for all weighted routes.</p>
</td>
<td>
No

View File

@ -1749,6 +1749,24 @@ No
was established. If not set, there is no max duration. When max_connection_duration
is reached the connection will be closed. Duration must be at least 1ms.</p>
</td>
<td>
No
</td>
</tr>
<tr id="ConnectionPoolSettings-TCPSettings-idle_timeout">
<td><code>idleTimeout</code></td>
<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#duration">Duration</a></code></td>
<td>
<p>The idle timeout for TCP connections.
The idle timeout is defined as the period in which there are no bytes sent or received on either
the upstream or downstream connection.
If not set, the default idle timeout is 1 hour. If set to 0s, the timeout will be disabled.
Idle timeout is not configured per each cluster individually when weighted destinations are used,
because idleTimeout is a property of a listener, not a cluster. In that case, idleTimeout
specified in a destination rule for the first weighted route is configured in the listener,
which means also for all weighted routes.</p>
</td>
<td>
No