mirror of https://github.com/istio/istio.io.git
Automator: update istio.io@ reference docs (#15826)
This commit is contained in:
parent
78594c4b8a
commit
02797767ce
|
|
@ -710,6 +710,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_USER</code></td>
|
||||
<td>String</td>
|
||||
<td><code>istio-proxy</code></td>
|
||||
|
|
|
|||
|
|
@ -333,7 +333,7 @@ debug and diagnose their Istio mesh.
|
|||
<td>Process directory arguments recursively. Useful when you want to analyze related manifests organized within the same directory. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--remote-cluster-context <stringArray></code></td>
|
||||
<td><code>--remote-contexts <stringArray></code></td>
|
||||
<td></td>
|
||||
<td>Kubernetes configuration contexts for remote clusters to be used in multi-cluster analysis. Not to be confused with '--context'. If unspecified, contexts are read from the remote secrets in the cluster. (default `[]`)</td>
|
||||
</tr>
|
||||
|
|
@ -7981,6 +7981,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>EXCLUDE_UNSAFE_503_FROM_DEFAULT_RETRY</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
|
|||
|
|
@ -1073,6 +1073,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_PROMETHEUS_PORT</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>15090</code></td>
|
||||
|
|
|
|||
|
|
@ -656,6 +656,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>EXCLUDE_UNSAFE_503_FROM_DEFAULT_RETRY</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
|
|||
|
|
@ -710,6 +710,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_USER</code></td>
|
||||
<td>String</td>
|
||||
<td><code>istio-proxy</code></td>
|
||||
|
|
|
|||
|
|
@ -333,7 +333,7 @@ debug and diagnose their Istio mesh.
|
|||
<td>Process directory arguments recursively. Useful when you want to analyze related manifests organized within the same directory. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>--remote-cluster-context <stringArray></code></td>
|
||||
<td><code>--remote-contexts <stringArray></code></td>
|
||||
<td></td>
|
||||
<td>Kubernetes configuration contexts for remote clusters to be used in multi-cluster analysis. Not to be confused with '--context'. If unspecified, contexts are read from the remote secrets in the cluster. (default `[]`)</td>
|
||||
</tr>
|
||||
|
|
@ -7981,6 +7981,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>EXCLUDE_UNSAFE_503_FROM_DEFAULT_RETRY</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
|
|||
|
|
@ -1073,6 +1073,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_PROMETHEUS_PORT</code></td>
|
||||
<td>Integer</td>
|
||||
<td><code>15090</code></td>
|
||||
|
|
|
|||
|
|
@ -656,6 +656,12 @@ https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/security/ssl#fip
|
|||
<td>If true, will use optimized vtprotobuf based marshaling. Requires a build with -tags=vtprotobuf.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ENVOY_DNS_JITTER_DURATION</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>Jitter added to periodic DNS resolution</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>EXCLUDE_UNSAFE_503_FROM_DEFAULT_RETRY</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
|
|
|||
Loading…
Reference in New Issue