mirror of https://github.com/istio/istio.io.git
Automator: update istio.io@ reference docs (#10041)
This commit is contained in:
parent
f4edd15af1
commit
e1e31d4a15
|
@ -6335,7 +6335,7 @@ These environment variables affect the behavior of the <code>istioctl</code> com
|
|||
<td><code>PILOT_DEBOUNCE_AFTER</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this internal. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this interval. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_DEBOUNCE_MAX</code></td>
|
||||
|
@ -6398,6 +6398,12 @@ These environment variables affect the behavior of the <code>istioctl</code> com
|
|||
<td>If enabled, pilot will wait for the completion of a receive operation beforeexecuting a push operation. This is a form of flow control and is useful inenvironments with high rates of push requests to each gateway. By default,this is false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_GATEWAY_API_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
@ -6608,6 +6614,12 @@ These environment variables affect the behavior of the <code>istioctl</code> com
|
|||
<td>If status is enabled, controls the QPS with which status will be updated. See https://godoc.org/k8s.io/client-go/rest#Config QPS</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_STATUS_UPDATE_INTERVAL</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>500ms</code></td>
|
||||
<td>Interval to update the XDS distribution status.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_TRACE_SAMPLING</code></td>
|
||||
<td>Floating-Point</td>
|
||||
<td><code>1</code></td>
|
||||
|
|
|
@ -287,7 +287,7 @@ These environment variables affect the behavior of the <code>operator</code> com
|
|||
<td><code>PILOT_DEBOUNCE_AFTER</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this internal. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this interval. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_DEBOUNCE_MAX</code></td>
|
||||
|
@ -350,6 +350,12 @@ These environment variables affect the behavior of the <code>operator</code> com
|
|||
<td>If enabled, pilot will wait for the completion of a receive operation beforeexecuting a push operation. This is a form of flow control and is useful inenvironments with high rates of push requests to each gateway. By default,this is false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_GATEWAY_API_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
@ -560,6 +566,12 @@ These environment variables affect the behavior of the <code>operator</code> com
|
|||
<td>If status is enabled, controls the QPS with which status will be updated. See https://godoc.org/k8s.io/client-go/rest#Config QPS</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_STATUS_UPDATE_INTERVAL</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>500ms</code></td>
|
||||
<td>Interval to update the XDS distribution status.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_TRACE_SAMPLING</code></td>
|
||||
<td>Floating-Point</td>
|
||||
<td><code>1</code></td>
|
||||
|
|
|
@ -888,7 +888,7 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
|
|||
<td><code>PILOT_DEBOUNCE_AFTER</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this internal. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this interval. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_DEBOUNCE_MAX</code></td>
|
||||
|
@ -951,6 +951,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
|
|||
<td>If enabled, pilot will wait for the completion of a receive operation beforeexecuting a push operation. This is a form of flow control and is useful inenvironments with high rates of push requests to each gateway. By default,this is false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_GATEWAY_API_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
@ -1161,6 +1167,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
|
|||
<td>If status is enabled, controls the QPS with which status will be updated. See https://godoc.org/k8s.io/client-go/rest#Config QPS</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_STATUS_UPDATE_INTERVAL</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>500ms</code></td>
|
||||
<td>Interval to update the XDS distribution status.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_TRACE_SAMPLING</code></td>
|
||||
<td>Floating-Point</td>
|
||||
<td><code>1</code></td>
|
||||
|
|
|
@ -495,7 +495,7 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
|
|||
<td><code>PILOT_DEBOUNCE_AFTER</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>100ms</code></td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this internal. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
<td>The delay added to config/registry events for debouncing. This will delay the push by at least this interval. If no change is detected within this period, the push will happen, otherwise we'll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_DEBOUNCE_MAX</code></td>
|
||||
|
@ -558,6 +558,12 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
|
|||
<td>If enabled, pilot will wait for the completion of a receive operation beforeexecuting a push operation. This is a form of flow control and is useful inenvironments with high rates of push requests to each gateway. By default,this is false.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_GATEWAY_API_STATUS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
<td>If this is set to true, gateway-api resources will have status written to them</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_ENABLE_HEADLESS_SERVICE_POD_LISTENERS</code></td>
|
||||
<td>Boolean</td>
|
||||
<td><code>true</code></td>
|
||||
|
@ -768,6 +774,12 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
|
|||
<td>If status is enabled, controls the QPS with which status will be updated. See https://godoc.org/k8s.io/client-go/rest#Config QPS</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_STATUS_UPDATE_INTERVAL</code></td>
|
||||
<td>Time Duration</td>
|
||||
<td><code>500ms</code></td>
|
||||
<td>Interval to update the XDS distribution status.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>PILOT_TRACE_SAMPLING</code></td>
|
||||
<td>Floating-Point</td>
|
||||
<td><code>1</code></td>
|
||||
|
|
Loading…
Reference in New Issue