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

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

@@ -3261,6 +3261,11 @@ Configure requires either the WorkloadGroup artifact path or its location on the
 <td>Creates a WorkloadEntry upon connection to istiod (if enabled in pilot). </td>
 </tr>
 <tr>
+<td><code>--capture-dns</code></td>
+<td></td>
+<td>Enables the capture of outgoing DNS packets on port 53, redirecting to istio-agent </td>
+</tr>
+<tr>
 <td><code>--clusterID &lt;string&gt;</code></td>
 <td></td>
 <td>The ID used to identify the cluster  (default `Kubernetes`)</td>
@@ -5737,7 +5742,7 @@ These environment variables affect the behavior of the <code>istioctl</code> com
 <tr>
 <td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
 <td>Boolean</td>
-<td><code>true</code></td>
+<td><code>false</code></td>
 <td></td>
 </tr>
 <tr>

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

@@ -413,7 +413,7 @@ These environment variables affect the behavior of the <code>operator</code> com
 <tr>
 <td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
 <td>Boolean</td>
-<td><code>true</code></td>
+<td><code>false</code></td>
 <td></td>
 </tr>
 <tr>

content/en/docs/reference/commands/pilot-agent/index.html

@@ -978,7 +978,7 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
 <tr>
 <td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
 <td>Boolean</td>
-<td><code>true</code></td>
+<td><code>false</code></td>
 <td></td>
 </tr>
 <tr>

content/en/docs/reference/commands/pilot-discovery/index.html

@@ -817,7 +817,7 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
 <tr>
 <td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
 <td>Boolean</td>
-<td><code>true</code></td>
+<td><code>false</code></td>
 <td></td>
 </tr>
 <tr>

content/en/docs/reference/config/istio.mesh.v1alpha1/index.html

@@ -1345,6 +1345,20 @@ matcher as follow:</p>
 collected by prometheus significantly. Care needs to be taken on Prometheus
 resource provision and configuration to reduce cardinality.</p>
 
+</td>
+<td>
+No
+</td>
+</tr>
+<tr id="ProxyConfig-hold_application_until_proxy_starts">
+<td><code>holdApplicationUntilProxyStarts</code></td>
+<td><code><a href="https://developers.google.com/protocol-buffers/docs/reference/google.protobuf#boolvalue">BoolValue</a></code></td>
+<td>
+<p>Boolean flag for enabling/disabling the holdApplicationUntilProxyStarts behavior.
+This feature adds hooks to delay application startup until the pod proxy
+is ready to accept traffic, mitigating some startup race conditions.
+Default value is &lsquo;false&rsquo;.</p>
+
 </td>
 <td>
 No

content/en/docs/reference/config/networking/envoy-filter/index.html

@@ -844,7 +844,7 @@ to <code>ROUTE_CONFIGURATION</code>, or <code>HTTP_ROUTE</code>.</p>
 <td><code>REMOVE</code></td>
 <td>
 <p>Remove the selected object from the list (of listeners,
-clusters, virtual hosts, network filters, or http
+clusters, virtual hosts, network filters, routes, or http
 filters). Does not require a value to be specified. This
 operation will be ignored when <code>applyTo</code> is set to
 <code>ROUTE_CONFIGURATION</code>, or <code>HTTP_ROUTE</code>.</p>
@@ -855,8 +855,10 @@ operation will be ignored when <code>applyTo</code> is set to
 <td><code>INSERT_BEFORE</code></td>
 <td>
 <p>Insert operation on an array of named objects. This operation
-is typically useful only in the context of filters, where the
+is typically useful only in the context of filters or routes,
-order of filters matter. For clusters and virtual hosts,
+where the order of elements matter. Routes should be ordered
+based on most to least specific matching criteria since the
+first matching element is selected. For clusters and virtual hosts,
 order of the element in the array does not matter. Insert
 before the selected filter or sub filter. If no filter is
 selected, the specified filter will be inserted at the front
@@ -868,8 +870,10 @@ of the list.</p>
 <td><code>INSERT_AFTER</code></td>
 <td>
 <p>Insert operation on an array of named objects. This operation
-is typically useful only in the context of filters, where the
+is typically useful only in the context of filters or routes,
-order of filters matter. For clusters and virtual hosts,
+where the order of elements matter. Routes should be ordered
+based on most to least specific matching criteria since the
+first matching element is selected. For clusters and virtual hosts,
 order of the element in the array does not matter. Insert
 after the selected filter or sub filter. If no filter is
 selected, the specified filter will be inserted at the end
@@ -881,8 +885,10 @@ of the list.</p>
 <td><code>INSERT_FIRST</code></td>
 <td>
 <p>Insert operation on an array of named objects. This operation
-is typically useful only in the context of filters, where the
+is typically useful only in the context of filters or routes,
-order of filters matter. For clusters and virtual hosts,
+where the order of elements matter. Routes should be ordered
+based on most to least specific matching criteria since the
+first matching element is selected. For clusters and virtual hosts,
 order of the element in the array does not matter. Insert
 first in the list based on the presence of selected filter or not.
 This is specifically useful when you want your filter first in the
@@ -1024,8 +1030,7 @@ route configuration objects.</p>
 <td><code>HTTP_ROUTE</code></td>
 <td>
 <p>Applies the patch to a route object inside the matched virtual
-host in a route configuration. Currently, only <code>MERGE</code> operation
+host in a route configuration.</p>
-is allowed on the route objects.</p>
 
 </td>
 </tr>