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

content/en/docs/reference/commands/istioctl/index.html

@@ -405,7 +405,7 @@ All names except label and annotation keys support '*' glob matching pat
 <tr>
 <td><code>--exclude &lt;stringSlice&gt;</code></td>
 <td></td>
-<td>Spec for which pod&#39;s proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples.  (default `["kube-system,kube-public,kube-node-lease,local-path-storage"]`)</td>
+<td>Spec for which pod&#39;s proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples.  (default `["kube-node-lease,local-path-storage,kube-system,kube-public"]`)</td>
 </tr>
 <tr>
 <td><code>--filename &lt;string&gt;</code></td>
@@ -510,7 +510,7 @@ All names except label and annotation keys support &#39;*&#39; glob matching pat
 <tr>
 <td><code>--exclude &lt;stringSlice&gt;</code></td>
 <td></td>
-<td>Spec for which pod&#39;s proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples.  (default `["kube-system,kube-public,kube-node-lease,local-path-storage"]`)</td>
+<td>Spec for which pod&#39;s proxy logs to exclude from the archive, after the include spec is processed. See above for format and examples.  (default `["kube-node-lease,local-path-storage,kube-system,kube-public"]`)</td>
 </tr>
 <tr>
 <td><code>--filename &lt;string&gt;</code></td>

content/en/docs/reference/config/networking/virtual-service/index.html

@@ -1696,10 +1696,9 @@ Yes
 <td><code>weight</code></td>
 <td><code>int32</code></td>
 <td>
-<p>The proportion of traffic to be forwarded to the service
-version. (0-100). Sum of weights across destinations SHOULD BE == 100.
-If there is only one destination in a rule, the weight value is assumed to
-be 100.</p>
+<p>Weight specifies the relative proportion of traffic to be forwarded to the destination. A destination will receive <code>weight/(sum of all weights)</code> requests.
+If there is only one destination in a rule, it will receive all traffic.
+Otherwise, if weight is <code>0</code>, the destination will not receive any traffic.</p>
 
 </td>
 <td>
@@ -1750,9 +1749,9 @@ Yes
 <td><code>weight</code></td>
 <td><code>int32</code></td>
 <td>
-<p>The proportion of traffic to be forwarded to the service
-version. If there is only one destination in a rule, all traffic will be
-routed to it irrespective of the weight.</p>
+<p>Weight specifies the relative proportion of traffic to be forwarded to the destination. A destination will receive <code>weight/(sum of all weights)</code> requests.
+If there is only one destination in a rule, it will receive all traffic.
+Otherwise, if weight is <code>0</code>, the destination will not receive any traffic.</p>
 
 </td>
 <td>

content/en/docs/reference/config/telemetry/index.html

@@ -21,10 +21,13 @@ to have a single workload selector-less Telemetry resource.</p>
 <p>For resources with a workload selector, it is only valid to have one resource selecting
 any given workload.</p>
 
-<p>The hierarchy of Telemetry configuration is as follows:
-1. Workload-specific configuration
-1. Namespace-specific configuration
-1. Root namespace configuration</p>
+<p>The hierarchy of Telemetry configuration is as follows:</p>
+
+<ol>
+<li>Workload-specific configuration</li>
+<li>Namespace-specific configuration</li>
+<li>Root namespace configuration</li>
+</ol>
 
 <p>Examples:</p>
 
@@ -828,10 +831,14 @@ No
 <td><code>expression</code></td>
 <td><code>string</code></td>
 <td>
-<p>CEL expression for selecting when requests/connections should be logged.
-Examples:
-- <code>response.code &gt;= 400</code>
-- <code>connection.mtls &amp;&amp; request.url_path.contains('v1beta3')</code></p>
+<p>CEL expression for selecting when requests/connections should be logged.</p>
+
+<p>Examples:</p>
+
+<ul>
+<li><code>response.code &gt;= 400</code></li>
+<li><code>connection.mtls &amp;&amp; request.url_path.contains('v1beta3')</code></li>
+</ul>
 
 </td>
 <td>
@@ -868,9 +875,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_requests_total</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/request_count</code> (SERVER mode)
-- <code>istio.io/service/client/request_count</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/request_count</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/request_count</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -881,9 +891,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_request_duration_milliseconds</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/response_latencies</code> (SERVER mode)
-- <code>istio.io/service/client/roundtrip_latencies</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/response_latencies</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/roundtrip_latencies</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -894,9 +907,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_request_bytes</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/request_bytes</code> (SERVER mode)
-- <code>istio.io/service/client/request_bytes</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/request_bytes</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/request_bytes</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -907,9 +923,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_response_bytes</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/response_bytes</code> (SERVER mode)
-- <code>istio.io/service/client/response_bytes</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/response_bytes</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/response_bytes</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -920,9 +939,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_tcp_connections_opened_total</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/connection_open_count</code> (SERVER mode)
-- <code>istio.io/service/client/connection_open_count</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/connection_open_count</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/connection_open_count</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -933,9 +955,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_tcp_connections_closed_total</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/connection_close_count</code> (SERVER mode)
-- <code>istio.io/service/client/connection_close_count</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/connection_close_count</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/connection_close_count</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -946,9 +971,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_tcp_sent_bytes_total</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/sent_bytes_count</code> (SERVER mode)
-- <code>istio.io/service/client/sent_bytes_count</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/sent_bytes_count</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/sent_bytes_count</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>
@@ -959,9 +987,12 @@ See also: https://istio.io/latest/docs/reference/config/metrics/#metrics</p>
 
 <p>The Prometheus provider exports this metric as: <code>istio_tcp_received_bytes_total</code>.</p>
 
-<p>The Stackdriver provider exports this metric as:
-- <code>istio.io/service/server/received_bytes_count</code> (SERVER mode)
-- <code>istio.io/service/client/received_bytes_count</code> (CLIENT mode)</p>
+<p>The Stackdriver provider exports this metric as:</p>
+
+<ul>
+<li><code>istio.io/service/server/received_bytes_count</code> (SERVER mode)</li>
+<li><code>istio.io/service/client/received_bytes_count</code> (CLIENT mode)</li>
+</ul>
 
 </td>
 </tr>