Initial reference doc update after moving preliminary back to master (#9781)

This commit is contained in:
Eric Van Norman 2021-05-18 14:05:01 -05:00 committed by GitHub
parent 300c819fdf
commit 691a6bb613
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
11 changed files with 358 additions and 150 deletions

View File

@ -1142,7 +1142,7 @@ Use 'add-to-mesh' as an alternate to namespace-wide auto injection for t
<p>&#39;istioctl experimental add-to-mesh deployment&#39; restarts pods with the Istio sidecar. Use &#39;add-to-mesh&#39;
to test deployments for compatibility with Istio. It can be used instead of namespace-wide auto-injection of sidecars and is especially helpful for compatibility testing.</p>
<p>If your deployment does not function after using &#39;add-to-mesh&#39; you must re-deploy it and troubleshoot it for Istio compatibility.
See https://istio.io/v1.10/docs/ops/deployment/requirements/</p>
See https://istio.io/v1.11/docs/ops/deployment/requirements/</p>
<p>See also &#39;istioctl experimental remove-from-mesh deployment&#39; which does the reverse.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental add-to-mesh deployment &lt;deployment&gt; [flags]
@ -1313,7 +1313,7 @@ The typical usage scenario is Mesh Expansion on VMs.</p>
<p>istioctl experimental add-to-mesh service restarts pods with the Istio sidecar. Use &#39;add-to-mesh&#39;
to test deployments for compatibility with Istio. It can be used instead of namespace-wide auto-injection of sidecars and is especially helpful for compatibility testing.</p>
<p>If your service does not function after using &#39;add-to-mesh&#39; you must re-deploy it and troubleshoot it for Istio compatibility.
See https://istio.io/v1.10/docs/ops/deployment/requirements/</p>
See https://istio.io/v1.11/docs/ops/deployment/requirements/</p>
<p>See also &#39;istioctl experimental remove-from-mesh service&#39; which does the reverse.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental add-to-mesh service &lt;service&gt; [flags]
@ -1604,8 +1604,8 @@ from multiple sources (mesh-level, namespace-level and workload-level).</p>
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -1878,6 +1878,11 @@ THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
</thead>
<tbody>
<tr>
<td><code>--all</code></td>
<td></td>
<td>Send the same request to all instances of Istiod. Only applicable for in-cluster deployment. </td>
</tr>
<tr>
<td><code>--authority &lt;string&gt;</code></td>
<td></td>
<td>XDS Subject Alternative Name (for example istiod.istio-system.svc) (default ``)</td>
@ -1947,18 +1952,24 @@ THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<h3 id="istioctl-experimental-internal-debug Examples">Examples</h3>
<pre class="language-bash"><code> # Retrieve sync status for all Envoys in a mesh
istioctl x internal-debug syncz
# Retrieve sync diff for a single Envoy and Istiod
istioctl x internal-debug syncz istio-egressgateway-59585c5b9c-ndc59.istio-system
# SECURITY OPTIONS
# Retrieve syncz debug information directly from the control plane, using token security
# (This is the usual way to get the debug information with an out-of-cluster control plane.)
istioctl x internal-debug syncz --xds-address istio.cloudprovider.example.com:15012
# Retrieve syncz debug information via Kubernetes config, using token security
# (This is the usual way to get the debug information with an in-cluster control plane.)
istioctl x internal-debug syncz
# Retrieve syncz debug information directly from the control plane, using RSA certificate security
# (Certificates must be obtained before this step. The --cert-dir flag lets istioctl bypass the Kubernetes API server.)
istioctl x internal-debug syncz --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs
# Retrieve syncz information via XDS from specific control plane in multi-control plane in-cluster configuration
# (Select a specific control plane in an in-cluster canary Istio configuration.)
istioctl x internal-debug syncz --xds-label istio.io/rev=default
@ -2474,8 +2485,8 @@ The typical usage scenario is Mesh Expansion on VMs.</p>
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2527,8 +2538,8 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2592,8 +2603,8 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2662,8 +2673,8 @@ without manual relabeling of the &#34;istio.io/rev&#34; tag.
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2716,8 +2727,8 @@ injection labels.</p>
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2808,8 +2819,8 @@ If set to true, the user is not prompted and a Yes response is assumed in all ca
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2871,8 +2882,8 @@ revision tag before removing using the &#34;istioctl x revision tag list&#34; co
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -2936,8 +2947,8 @@ injection labels.</p>
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -3013,6 +3024,11 @@ If set to true, the user is not prompted and a Yes response is assumed in all ca
<td>The name of the kubeconfig context to use (default ``)</td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td></td>
<td>Console/log output only, make no changes. </td>
</tr>
<tr>
<td><code>--filename &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>The filename of the IstioOperator CR. (default ``)</td>
@ -3036,8 +3052,8 @@ If set to true, the user is not prompted and a Yes response is assumed in all ca
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -3060,7 +3076,7 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>-s</code></td>
<td>Override an IstioOperator value, e.g. to choose a profile
(--set profile=demo), enable or disable components (--set components.cni.enabled=true), or override Istio
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.10/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.11/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
@ -3427,6 +3443,11 @@ Configure requires either the WorkloadGroup artifact path or its location on the
<td></td>
<td>The token duration in seconds (default: 1 hour) (default `3600`)</td>
</tr>
<tr>
<td><code>--workloadIP &lt;string&gt;</code></td>
<td></td>
<td>IP address of the workload used in the WorkloadEntry (default ``)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload-entry-configure Examples">Examples</h3>
@ -3592,8 +3613,8 @@ This flag can be specified multiple times to overlay multiple files. Multiple fi
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -3616,7 +3637,7 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>-s</code></td>
<td>Override an IstioOperator value, e.g. to choose a profile
(--set profile=demo), enable or disable components (--set components.cni.enabled=true), or override Istio
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.10/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.11/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
@ -3647,18 +3668,12 @@ If set to true, the user is not prompted and a Yes response is assumed in all ca
</code></pre>
<h2 id="istioctl-kube-inject">istioctl kube-inject</h2>
<p>
kube-inject manually injects the Envoy sidecar into Kubernetes
kube-inject manually injects the Istio sidecar into Kubernetes
workloads. Unsupported resources are left unmodified so it is safe to
run kube-inject over a single file that contains multiple Service,
ConfigMap, Deployment, etc. definitions for a complex application. It&#39;s
best to do this when the resource is initially created.</p>
<p>k8s.io/docs/concepts/workloads/pods/pod-overview/#pod-templates is
updated for Job, DaemonSet, ReplicaSet, Pod and Deployment YAML resource
documents. Support for additional pod-based resource types can be
added as necessary.</p>
<p>The Istio project is continually evolving so the Istio sidecar
configuration may change unannounced. When in doubt re-run istioctl
kube-inject on deployments to get the most up-to-date changes.
ConfigMap, Deployment, etc. definitions for a complex application. When in
doubt re-run istioctl kube-inject on deployments to get the most up-to-date changes.</p>
<p>It&#39;s best to do kube-inject when the resource is initially created.
</p>
<pre class="language-bash"><code>istioctl kube-inject [flags]
</code></pre>
@ -3737,7 +3752,7 @@ kube-inject on deployments to get the most up-to-date changes.
<pre class="language-bash"><code> # Update resources on the fly before applying.
kubectl apply -f &lt;(istioctl kube-inject -f &lt;resource.yaml&gt;)
# Create a persistent version of the deployment with Envoy sidecar injected.
# Create a persistent version of the deployment with Istio sidecar injected.
istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml
# Update an existing deployment.
@ -3925,8 +3940,8 @@ This flag can be specified multiple times to overlay multiple files. Multiple fi
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -3949,7 +3964,7 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>-s</code></td>
<td>Override an IstioOperator value, e.g. to choose a profile
(--set profile=demo), enable or disable components (--set components.cni.enabled=true), or override Istio
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.10/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.11/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
</tr>
</tbody>
</table>
@ -4023,8 +4038,8 @@ This flag can be specified multiple times to overlay multiple files. Multiple fi
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -4047,7 +4062,7 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>-s</code></td>
<td>Override an IstioOperator value, e.g. to choose a profile
(--set profile=demo), enable or disable components (--set components.cni.enabled=true), or override Istio
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.10/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.11/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
@ -4162,8 +4177,8 @@ could be secret list separated by comma, eg. &#39;--imagePullSecrets imagePullSe
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -4247,8 +4262,8 @@ could be secret list separated by comma, eg. &#39;--imagePullSecrets imagePullSe
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -4450,8 +4465,8 @@ istioctl install --set profile=demo # Use a profile from the list
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -4521,8 +4536,8 @@ This flag can be specified multiple times to overlay multiple files. Multiple fi
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -4579,8 +4594,8 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -5372,8 +5387,8 @@ This flag can be specified multiple times to overlay multiple files. Multiple fi
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -5391,7 +5406,7 @@ or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/i
<td><code>-s</code></td>
<td>Override an IstioOperator value, e.g. to choose a profile
(--set profile=demo), enable or disable components (--set components.cni.enabled=true), or override Istio
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.10/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
settings (--set meshConfig.enableTracing=true). See documentation for more info:https://istio.io/v1.11/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
@ -5516,8 +5531,8 @@ istioctl experimental precheck.
<td><code>--manifests &lt;string&gt;</code></td>
<td><code>-d</code></td>
<td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.10.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.10/istio-1.10-linux-amd64.tar.gz).
(e.g. ~/Downloads/istio-1.11.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.11/istio-1.11-linux-amd64.tar.gz).
(default ``)</td>
</tr>
<tr>
@ -5637,6 +5652,12 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<td>If true, Istiod will set the pod fsGroup to 1337 on injection. This is required for Kubernetes 1.18 and older (see https://github.com/kubernetes/kubernetes/issues/57923 for details) unless JWT_POLICY is &#34;first-party-jwt&#34;.</td>
</tr>
<tr>
<td><code>ENABLE_MULTICLUSTER_HEADLESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, the DNS name table for a headless service will resolve to same-network endpoints in any cluster.</td>
</tr>
<tr>
<td><code>ENABLE_WASM_TELEMETRY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -5721,18 +5742,18 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<td>Custom host name of istiod that istiod signs the server cert.</td>
</tr>
<tr>
<td><code>ISTIOD_ENABLE_SDS_SERVER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istiod will serve SDS for credentialName secrets (rather than in-proxy). To ensure proper security, PILOT_ENABLE_XDS_IDENTITY_CHECK=true is required as well.</td>
</tr>
<tr>
<td><code>ISTIO_AGENT_ENABLE_WASM_REMOTE_LOAD_CONVERSION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istio agent will intercept ECDS resource update, downloads Wasm module, and replaces Wasm module remote load with downloaded local module file.</td>
</tr>
<tr>
<td><code>ISTIO_BOOTSTRAP</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>ISTIO_DEFAULT_REQUEST_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>0s</code></td>
@ -5793,12 +5814,6 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<td>KNative revision, set if running in knative</td>
</tr>
<tr>
<td><code>PILOT_ALLOW_METADATA_CERTS_DR_MUTUAL_TLS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will allow certs specified in Metadata to override DR certs in MUTUAL TLS mode. This is only enabled for migration and will be removed soon.</td>
</tr>
<tr>
<td><code>PILOT_CERT_PROVIDER</code></td>
<td>String</td>
<td><code>istiod</code></td>
@ -5979,6 +5994,12 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<td>If true, pilot will add telemetry related metadata to Endpoint resource, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENVOY_FILTER_STATS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will collect metrics for envoy filter operations.</td>
</tr>
<tr>
<td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -5997,6 +6018,12 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<td>Enables the use of HTTP 1.0 in the outbound HTTP listeners, to support legacy applications.</td>
</tr>
<tr>
<td><code>PILOT_HTTP_DELAYED_CLOSE_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
<td>The delayed close timeout is for downstream HTTP connections. This should be set to a high value or disable it when peer is reading large chunk of data and to give an opportunity to initiate the close sequence properly. A value of 0s disables this</td>
</tr>
<tr>
<td><code>PILOT_INBOUND_PROTOCOL_DETECTION_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
@ -6095,7 +6122,7 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<tr>
<td><code>PILOT_XDS_SEND_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>5s</code></td>
<td><code>0s</code></td>
<td>The timeout to send the XDS configuration to proxies. After this timeout is reached, Pilot will discard that push.</td>
</tr>
<tr>
@ -6218,7 +6245,6 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<tr><td><code>pilot_eds_no_instances</code></td><td><code>LastValue</code></td><td>Number of clusters without instances.</td></tr>
<tr><td><code>pilot_endpoint_not_ready</code></td><td><code>LastValue</code></td><td>Endpoint found in unready state.</td></tr>
<tr><td><code>pilot_inbound_updates</code></td><td><code>Sum</code></td><td>Total number of updates received by pilot.</td></tr>
<tr><td><code>pilot_invalid_out_listeners</code></td><td><code>LastValue</code></td><td>Number of invalid outbound listeners.</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_fail_total</code></td><td><code>Sum</code></td><td>Total number of failed network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_success_total</code></td><td><code>Sum</code></td><td>Total number of successfully network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_k8s_cfg_events</code></td><td><code>Sum</code></td><td>Events from k8s config.</td></tr>
@ -6238,6 +6264,7 @@ These environment variables affect the behavior of the <code>istioctl</code> com
<tr><td><code>pilot_vservice_dup_domain</code></td><td><code>LastValue</code></td><td>Virtual services with dup domains.</td></tr>
<tr><td><code>pilot_xds</code></td><td><code>LastValue</code></td><td>Number of endpoints connected to this pilot using XDS.</td></tr>
<tr><td><code>pilot_xds_cds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected CDS configs.</td></tr>
<tr><td><code>pilot_xds_config_size_bytes</code></td><td><code>Distribution</code></td><td>Distribution of configuration sizes pushed to clients</td></tr>
<tr><td><code>pilot_xds_delayed_push_timeouts_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed and timed out</td></tr>
<tr><td><code>pilot_xds_delayed_pushes_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed.</td></tr>
<tr><td><code>pilot_xds_eds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected EDS.</td></tr>

View File

@ -152,6 +152,12 @@ These environment variables affect the behavior of the <code>operator</code> com
<td>If true, Istiod will set the pod fsGroup to 1337 on injection. This is required for Kubernetes 1.18 and older (see https://github.com/kubernetes/kubernetes/issues/57923 for details) unless JWT_POLICY is &#34;first-party-jwt&#34;.</td>
</tr>
<tr>
<td><code>ENABLE_MULTICLUSTER_HEADLESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, the DNS name table for a headless service will resolve to same-network endpoints in any cluster.</td>
</tr>
<tr>
<td><code>ENABLE_WASM_TELEMETRY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -182,18 +188,18 @@ These environment variables affect the behavior of the <code>operator</code> com
<td>Custom host name of istiod that istiod signs the server cert.</td>
</tr>
<tr>
<td><code>ISTIOD_ENABLE_SDS_SERVER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istiod will serve SDS for credentialName secrets (rather than in-proxy). To ensure proper security, PILOT_ENABLE_XDS_IDENTITY_CHECK=true is required as well.</td>
</tr>
<tr>
<td><code>ISTIO_AGENT_ENABLE_WASM_REMOTE_LOAD_CONVERSION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istio agent will intercept ECDS resource update, downloads Wasm module, and replaces Wasm module remote load with downloaded local module file.</td>
</tr>
<tr>
<td><code>ISTIO_BOOTSTRAP</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>ISTIO_DEFAULT_REQUEST_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>0s</code></td>
@ -248,12 +254,6 @@ These environment variables affect the behavior of the <code>operator</code> com
<td>KNative revision, set if running in knative</td>
</tr>
<tr>
<td><code>PILOT_ALLOW_METADATA_CERTS_DR_MUTUAL_TLS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will allow certs specified in Metadata to override DR certs in MUTUAL TLS mode. This is only enabled for migration and will be removed soon.</td>
</tr>
<tr>
<td><code>PILOT_CERT_PROVIDER</code></td>
<td>String</td>
<td><code>istiod</code></td>
@ -434,6 +434,12 @@ These environment variables affect the behavior of the <code>operator</code> com
<td>If true, pilot will add telemetry related metadata to Endpoint resource, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENVOY_FILTER_STATS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will collect metrics for envoy filter operations.</td>
</tr>
<tr>
<td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -452,6 +458,12 @@ These environment variables affect the behavior of the <code>operator</code> com
<td>Enables the use of HTTP 1.0 in the outbound HTTP listeners, to support legacy applications.</td>
</tr>
<tr>
<td><code>PILOT_HTTP_DELAYED_CLOSE_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
<td>The delayed close timeout is for downstream HTTP connections. This should be set to a high value or disable it when peer is reading large chunk of data and to give an opportunity to initiate the close sequence properly. A value of 0s disables this</td>
</tr>
<tr>
<td><code>PILOT_INBOUND_PROTOCOL_DETECTION_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
@ -550,7 +562,7 @@ These environment variables affect the behavior of the <code>operator</code> com
<tr>
<td><code>PILOT_XDS_SEND_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>5s</code></td>
<td><code>0s</code></td>
<td>The timeout to send the XDS configuration to proxies. After this timeout is reached, Pilot will discard that push.</td>
</tr>
<tr>
@ -647,7 +659,6 @@ These environment variables affect the behavior of the <code>operator</code> com
<tr><td><code>pilot_eds_no_instances</code></td><td><code>LastValue</code></td><td>Number of clusters without instances.</td></tr>
<tr><td><code>pilot_endpoint_not_ready</code></td><td><code>LastValue</code></td><td>Endpoint found in unready state.</td></tr>
<tr><td><code>pilot_inbound_updates</code></td><td><code>Sum</code></td><td>Total number of updates received by pilot.</td></tr>
<tr><td><code>pilot_invalid_out_listeners</code></td><td><code>LastValue</code></td><td>Number of invalid outbound listeners.</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_fail_total</code></td><td><code>Sum</code></td><td>Total number of failed network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_success_total</code></td><td><code>Sum</code></td><td>Total number of successfully network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_k8s_cfg_events</code></td><td><code>Sum</code></td><td>Events from k8s config.</td></tr>
@ -667,6 +678,7 @@ These environment variables affect the behavior of the <code>operator</code> com
<tr><td><code>pilot_vservice_dup_domain</code></td><td><code>LastValue</code></td><td>Virtual services with dup domains.</td></tr>
<tr><td><code>pilot_xds</code></td><td><code>LastValue</code></td><td>Number of endpoints connected to this pilot using XDS.</td></tr>
<tr><td><code>pilot_xds_cds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected CDS configs.</td></tr>
<tr><td><code>pilot_xds_config_size_bytes</code></td><td><code>Distribution</code></td><td>Distribution of configuration sizes pushed to clients</td></tr>
<tr><td><code>pilot_xds_delayed_push_timeouts_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed and timed out</td></tr>
<tr><td><code>pilot_xds_delayed_pushes_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed.</td></tr>
<tr><td><code>pilot_xds_eds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected EDS.</td></tr>

View File

@ -149,6 +149,11 @@ remove_toc_prefix: 'pilot-agent '
</thead>
<tbody>
<tr>
<td><code>--capture-all-dns</code></td>
<td></td>
<td>Instead of only capturing DNS traffic to DNS server IP, capture all DNS traffic at port 53. This setting is only effective when redirect dns is enabled. </td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td><code>-n</code></td>
<td>Do not call any external dependencies like iptables </td>
@ -594,6 +599,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
</thead>
<tbody>
<tr>
<td><code>BOOTSTRAP_XDS_AGENT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If set to true, agent retrieves the bootstrap configuration prior to starting Envoy</td>
</tr>
<tr>
<td><code>CA_ADDR</code></td>
<td>String</td>
<td><code></code></td>
@ -654,6 +665,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>If true, Istiod will set the pod fsGroup to 1337 on injection. This is required for Kubernetes 1.18 and older (see https://github.com/kubernetes/kubernetes/issues/57923 for details) unless JWT_POLICY is &#34;first-party-jwt&#34;.</td>
</tr>
<tr>
<td><code>ENABLE_MULTICLUSTER_HEADLESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, the DNS name table for a headless service will resolve to same-network endpoints in any cluster.</td>
</tr>
<tr>
<td><code>ENABLE_WASM_TELEMETRY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -708,12 +725,6 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>Custom host name of istiod that istiod signs the server cert.</td>
</tr>
<tr>
<td><code>ISTIOD_ENABLE_SDS_SERVER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istiod will serve SDS for credentialName secrets (rather than in-proxy). To ensure proper security, PILOT_ENABLE_XDS_IDENTITY_CHECK=true is required as well.</td>
</tr>
<tr>
<td><code>ISTIO_AGENT_ENABLE_WASM_REMOTE_LOAD_CONVERSION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
@ -822,12 +833,6 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>The output directory for the key and certificate. If empty, key and certificate will not be saved. Must be set for VMs using provisioning certificates.</td>
</tr>
<tr>
<td><code>PILOT_ALLOW_METADATA_CERTS_DR_MUTUAL_TLS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will allow certs specified in Metadata to override DR certs in MUTUAL TLS mode. This is only enabled for migration and will be removed soon.</td>
</tr>
<tr>
<td><code>PILOT_CERT_PROVIDER</code></td>
<td>String</td>
<td><code>istiod</code></td>
@ -1008,6 +1013,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>If true, pilot will add telemetry related metadata to Endpoint resource, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENVOY_FILTER_STATS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will collect metrics for envoy filter operations.</td>
</tr>
<tr>
<td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -1026,6 +1037,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>Enables the use of HTTP 1.0 in the outbound HTTP listeners, to support legacy applications.</td>
</tr>
<tr>
<td><code>PILOT_HTTP_DELAYED_CLOSE_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
<td>The delayed close timeout is for downstream HTTP connections. This should be set to a high value or disable it when peer is reading large chunk of data and to give an opportunity to initiate the close sequence properly. A value of 0s disables this</td>
</tr>
<tr>
<td><code>PILOT_INBOUND_PROTOCOL_DETECTION_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
@ -1124,7 +1141,7 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<tr>
<td><code>PILOT_XDS_SEND_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>5s</code></td>
<td><code>0s</code></td>
<td>The timeout to send the XDS configuration to proxies. After this timeout is reached, Pilot will discard that push.</td>
</tr>
<tr>
@ -1164,6 +1181,12 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<td>If set to true, agent retrieves dynamic proxy-config updates via xds channel</td>
</tr>
<tr>
<td><code>PROXY_XDS_DEBUG_VIA_AGENT</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If set to true, the agent will listen on 15009 and offer pilot&#39;s XDS istio.io/debug debug API there.</td>
</tr>
<tr>
<td><code>PROXY_XDS_VIA_AGENT</code></td>
<td>Boolean</td>
<td><code>true</code></td>
@ -1298,7 +1321,6 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<tr><td><code>pilot_eds_no_instances</code></td><td><code>LastValue</code></td><td>Number of clusters without instances.</td></tr>
<tr><td><code>pilot_endpoint_not_ready</code></td><td><code>LastValue</code></td><td>Endpoint found in unready state.</td></tr>
<tr><td><code>pilot_inbound_updates</code></td><td><code>Sum</code></td><td>Total number of updates received by pilot.</td></tr>
<tr><td><code>pilot_invalid_out_listeners</code></td><td><code>LastValue</code></td><td>Number of invalid outbound listeners.</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_fail_total</code></td><td><code>Sum</code></td><td>Total number of failed network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_success_total</code></td><td><code>Sum</code></td><td>Total number of successfully network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_k8s_cfg_events</code></td><td><code>Sum</code></td><td>Events from k8s config.</td></tr>
@ -1318,6 +1340,7 @@ These environment variables affect the behavior of the <code>pilot-agent</code>
<tr><td><code>pilot_vservice_dup_domain</code></td><td><code>LastValue</code></td><td>Virtual services with dup domains.</td></tr>
<tr><td><code>pilot_xds</code></td><td><code>LastValue</code></td><td>Number of endpoints connected to this pilot using XDS.</td></tr>
<tr><td><code>pilot_xds_cds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected CDS configs.</td></tr>
<tr><td><code>pilot_xds_config_size_bytes</code></td><td><code>Distribution</code></td><td>Distribution of configuration sizes pushed to clients</td></tr>
<tr><td><code>pilot_xds_delayed_push_timeouts_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed and timed out</td></tr>
<tr><td><code>pilot_xds_delayed_pushes_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed.</td></tr>
<tr><td><code>pilot_xds_eds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected EDS.</td></tr>

View File

@ -89,11 +89,6 @@ remove_toc_prefix: 'pilot-discovery '
</thead>
<tbody>
<tr>
<td><code>--appNamespace &lt;string&gt;</code></td>
<td><code>-a</code></td>
<td>Specify the applications namespace list the controller manages, separated by comma; if not set, controller watches all namespaces (default ``)</td>
</tr>
<tr>
<td><code>--caCertFile &lt;string&gt;</code></td>
<td></td>
<td>File containing the x509 Server CA Certificate (default ``)</td>
@ -264,6 +259,11 @@ remove_toc_prefix: 'pilot-discovery '
<td>Discovery service secured gRPC address (default `:15012`)</td>
</tr>
<tr>
<td><code>--shutdownDuration &lt;duration&gt;</code></td>
<td></td>
<td>Duration the discovery server needs to terminate gracefully (default `10s`)</td>
</tr>
<tr>
<td><code>--tls-cipher-suites &lt;stringSlice&gt;</code></td>
<td></td>
<td>Comma-separated list of cipher suites for istiod TLS server. If omitted, the default Go cipher suites will be used.
@ -526,6 +526,12 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<td>If true, Istiod will set the pod fsGroup to 1337 on injection. This is required for Kubernetes 1.18 and older (see https://github.com/kubernetes/kubernetes/issues/57923 for details) unless JWT_POLICY is &#34;first-party-jwt&#34;.</td>
</tr>
<tr>
<td><code>ENABLE_MULTICLUSTER_HEADLESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, the DNS name table for a headless service will resolve to same-network endpoints in any cluster.</td>
</tr>
<tr>
<td><code>ENABLE_WASM_TELEMETRY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -568,18 +574,18 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<td>Custom host name of istiod that istiod signs the server cert.</td>
</tr>
<tr>
<td><code>ISTIOD_ENABLE_SDS_SERVER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istiod will serve SDS for credentialName secrets (rather than in-proxy). To ensure proper security, PILOT_ENABLE_XDS_IDENTITY_CHECK=true is required as well.</td>
</tr>
<tr>
<td><code>ISTIO_AGENT_ENABLE_WASM_REMOTE_LOAD_CONVERSION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Istio agent will intercept ECDS resource update, downloads Wasm module, and replaces Wasm module remote load with downloaded local module file.</td>
</tr>
<tr>
<td><code>ISTIO_BOOTSTRAP</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>ISTIO_DEFAULT_REQUEST_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>0s</code></td>
@ -664,12 +670,6 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<td>The max TTL of issued workload certificates.</td>
</tr>
<tr>
<td><code>PILOT_ALLOW_METADATA_CERTS_DR_MUTUAL_TLS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will allow certs specified in Metadata to override DR certs in MUTUAL TLS mode. This is only enabled for migration and will be removed soon.</td>
</tr>
<tr>
<td><code>PILOT_CERT_PROVIDER</code></td>
<td>String</td>
<td><code>istiod</code></td>
@ -850,6 +850,12 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<td>If true, pilot will add telemetry related metadata to Endpoint resource, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENVOY_FILTER_STATS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will collect metrics for envoy filter operations.</td>
</tr>
<tr>
<td><code>PILOT_FILTER_GATEWAY_CLUSTER_CONFIG</code></td>
<td>Boolean</td>
<td><code>false</code></td>
@ -868,6 +874,12 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<td>Enables the use of HTTP 1.0 in the outbound HTTP listeners, to support legacy applications.</td>
</tr>
<tr>
<td><code>PILOT_HTTP_DELAYED_CLOSE_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
<td>The delayed close timeout is for downstream HTTP connections. This should be set to a high value or disable it when peer is reading large chunk of data and to give an opportunity to initiate the close sequence properly. A value of 0s disables this</td>
</tr>
<tr>
<td><code>PILOT_INBOUND_PROTOCOL_DETECTION_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
@ -966,7 +978,7 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<tr>
<td><code>PILOT_XDS_SEND_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>5s</code></td>
<td><code>0s</code></td>
<td>The timeout to send the XDS configuration to proxies. After this timeout is reached, Pilot will discard that push.</td>
</tr>
<tr>
@ -1121,7 +1133,6 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<tr><td><code>pilot_eds_no_instances</code></td><td><code>LastValue</code></td><td>Number of clusters without instances.</td></tr>
<tr><td><code>pilot_endpoint_not_ready</code></td><td><code>LastValue</code></td><td>Endpoint found in unready state.</td></tr>
<tr><td><code>pilot_inbound_updates</code></td><td><code>Sum</code></td><td>Total number of updates received by pilot.</td></tr>
<tr><td><code>pilot_invalid_out_listeners</code></td><td><code>LastValue</code></td><td>Number of invalid outbound listeners.</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_fail_total</code></td><td><code>Sum</code></td><td>Total number of failed network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_jwks_resolver_network_fetch_success_total</code></td><td><code>Sum</code></td><td>Total number of successfully network fetch by pilot jwks resolver</td></tr>
<tr><td><code>pilot_k8s_cfg_events</code></td><td><code>Sum</code></td><td>Events from k8s config.</td></tr>
@ -1141,6 +1152,7 @@ These environment variables affect the behavior of the <code>pilot-discovery</co
<tr><td><code>pilot_vservice_dup_domain</code></td><td><code>LastValue</code></td><td>Virtual services with dup domains.</td></tr>
<tr><td><code>pilot_xds</code></td><td><code>LastValue</code></td><td>Number of endpoints connected to this pilot using XDS.</td></tr>
<tr><td><code>pilot_xds_cds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected CDS configs.</td></tr>
<tr><td><code>pilot_xds_config_size_bytes</code></td><td><code>Distribution</code></td><td>Distribution of configuration sizes pushed to clients</td></tr>
<tr><td><code>pilot_xds_delayed_push_timeouts_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed and timed out</td></tr>
<tr><td><code>pilot_xds_delayed_pushes_total</code></td><td><code>Sum</code></td><td>Total number of XDS pushes that are delayed.</td></tr>
<tr><td><code>pilot_xds_eds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected EDS.</td></tr>

View File

@ -43,6 +43,19 @@ Istio supports to control its behavior.
<tr>
<td><code>inject.istio.io/templates</code></td>
<td>Alpha</td>
<td>[Pod]</td>
<td>The name of the inject template(s) to use, as a comma separate list. See https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#custom-templates-experimental for more information.</td>
</tr>
<tr>
<td><code>install.operator.istio.io/chart-owner</code></td>
@ -135,6 +148,8 @@ Istio supports to control its behavior.
<tr>

View File

@ -7,7 +7,7 @@ location: https://istio.io/docs/reference/config/istio.mesh.v1alpha1.html
layout: protoc-gen-docs
generator: protoc-gen-docs
weight: 20
number_of_entries: 44
number_of_entries: 45
---
<p>Configuration affecting the service mesh as a whole.</p>
@ -1047,6 +1047,17 @@ No
<td>
<p>Configures an OpenCensusAgent tracing provider.</p>
</td>
<td>
No
</td>
</tr>
<tr id="MeshConfig-ExtensionProvider-skywalking" class="oneof">
<td><code>skywalking</code></td>
<td><code><a href="#MeshConfig-ExtensionProvider-SkyWalkingTracingProvider">SkyWalkingTracingProvider (oneof)</a></code></td>
<td>
<p>Configures a Apache SkyWalking provider.</p>
</td>
<td>
No
@ -1669,6 +1680,61 @@ No
<p>Optional. Controls the overall path length allowed in a reported span.
NOTE: currently only controls max length of the path tag.</p>
</td>
<td>
No
</td>
</tr>
</tbody>
</table>
</section>
<h2 id="MeshConfig-ExtensionProvider-SkyWalkingTracingProvider">MeshConfig.ExtensionProvider.SkyWalkingTracingProvider</h2>
<section>
<p>Defines configuration for a SkyWalking tracer.</p>
<table class="message-fields">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Description</th>
<th>Required</th>
</tr>
</thead>
<tbody>
<tr id="MeshConfig-ExtensionProvider-SkyWalkingTracingProvider-service">
<td><code>service</code></td>
<td><code>string</code></td>
<td>
<p>REQUIRED. Specifies the service for the SkyWalking receiver.
The format is &ldquo;[<Namespace>/]<Hostname>&rdquo;. The specification of <Namespace> is required only when it is insufficient
to unambiguously resolve a service in the service registry. The <Hostname> is a fully qualified host name of a
service defined by the Kubernetes service or ServiceEntry.</p>
<p>Example: &ldquo;skywalking.default.svc.cluster.local&rdquo; or &ldquo;bar/skywalking.example.com&rdquo;.</p>
</td>
<td>
No
</td>
</tr>
<tr id="MeshConfig-ExtensionProvider-SkyWalkingTracingProvider-port">
<td><code>port</code></td>
<td><code>uint32</code></td>
<td>
<p>REQUIRED. Specifies the port of the service.</p>
</td>
<td>
No
</td>
</tr>
<tr id="MeshConfig-ExtensionProvider-SkyWalkingTracingProvider-access_token">
<td><code>accessToken</code></td>
<td><code>string</code></td>
<td>
<p>Optional. The SkyWalking OAP access token.</p>
</td>
<td>
No

View File

@ -1948,7 +1948,7 @@ No
<tbody>
<tr id="PodDisruptionBudgetSpec-minAvailable">
<td><code>minAvailable</code></td>
<td><code>uint32</code></td>
<td><code><a href="#TypeIntOrStringForPB">TypeIntOrStringForPB</a></code></td>
<td>
</td>
<td>
@ -1966,7 +1966,7 @@ No
</tr>
<tr id="PodDisruptionBudgetSpec-maxUnavailable">
<td><code>maxUnavailable</code></td>
<td><code>uint32</code></td>
<td><code><a href="#TypeIntOrStringForPB">TypeIntOrStringForPB</a></code></td>
<td>
</td>
<td>

View File

@ -490,36 +490,36 @@ the User cookie as the hash key.</p>
<p>{{<tabset category-name="example">}}
{{<tab name="v1alpha3" category-value="v1alpha3">}}</p>
<pre><code class="language-yaml"> apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
name: bookinfo-ratings
spec:
host: ratings.prod.svc.cluster.local
trafficPolicy:
loadBalancer:
consistentHash:
httpCookie:
name: user
ttl: 0s
<pre><code class="language-yaml">apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
name: bookinfo-ratings
spec:
host: ratings.prod.svc.cluster.local
trafficPolicy:
loadBalancer:
consistentHash:
httpCookie:
name: user
ttl: 0s
</code></pre>
<p>{{</tab>}}</p>
<p>{{<tab name="v1beta1" category-value="v1beta1">}}</p>
<pre><code class="language-yaml"> apiVersion: networking.istio.io/v1beta1
kind: DestinationRule
metadata:
name: bookinfo-ratings
spec:
host: ratings.prod.svc.cluster.local
trafficPolicy:
loadBalancer:
consistentHash:
httpCookie:
name: user
ttl: 0s
<pre><code class="language-yaml">apiVersion: networking.istio.io/v1beta1
kind: DestinationRule
metadata:
name: bookinfo-ratings
spec:
host: ratings.prod.svc.cluster.local
trafficPolicy:
loadBalancer:
consistentHash:
httpCookie:
name: user
ttl: 0s
</code></pre>
<p>{{</tab>}}
@ -732,6 +732,37 @@ spec:
</tr>
</thead>
<tbody>
<tr id="OutlierDetection-split_external_local_origin_errors">
<td><code>splitExternalLocalOriginErrors</code></td>
<td><code>bool</code></td>
<td>
<p>Determines whether to distinguish local origin failures from external errors. If set to true
consecutive<em>local</em>origin_failure is taken into account for outlier detection calculations.
This should be used when you want to derive the outlier detection status based on the errors
seen locally such as failure to connect, timeout while connecting etc. rather than the status code
retuned by upstream service. This is especially useful when the upstream service explicitly returns
a 5xx for some requests and you want to ignore those responses from upstream service while determining
the outlier detection status of a host.
Defaults to false.</p>
</td>
<td>
No
</td>
</tr>
<tr id="OutlierDetection-consecutive_local_origin_failure">
<td><code>consecutiveLocalOriginFailure</code></td>
<td><code><a href="#google-protobuf-UInt32Value">UInt32Value</a></code></td>
<td>
<p>The number of consecutive locally originated failures before ejection
occurs. Defaults to 5. Parameter takes effect only when split<em>external</em>local<em>origin</em>errors
is set to true.</p>
</td>
<td>
No
</td>
</tr>
<tr id="OutlierDetection-consecutive_gateway_errors">
<td><code>consecutiveGatewayErrors</code></td>
<td><code><a href="#google-protobuf-UInt32Value">UInt32Value</a></code></td>

View File

@ -341,7 +341,7 @@ and the namespace is &ldquo;prod&rdquo; or &ldquo;test&rdquo; and the ip is not
<pre><code class="language-yaml">principals: [&quot;admin&quot;, &quot;dev&quot;]
namespaces: [&quot;prod&quot;, &quot;test&quot;]
not_ipblocks: [&quot;1.2.3.4&quot;]
notIpBlocks: [&quot;1.2.3.4&quot;]
</code></pre>
<table class="message-fields">
@ -497,7 +497,7 @@ and the method is &ldquo;GET&rdquo; or &ldquo;HEAD&rdquo; and the path doesn&rsq
<pre><code class="language-yaml">hosts: [&quot;*.example.com&quot;]
methods: [&quot;GET&quot;, &quot;HEAD&quot;]
not_paths: [&quot;/admin*&quot;]
notPaths: [&quot;/admin*&quot;]
</code></pre>
<table class="message-fields">

View File

@ -442,7 +442,7 @@ messages:
- name: "LocalhostListener"
code: IST0143
level: Error
description: "A port exposed in by a Service is bound to a localhost address"
description: "A port exposed in a Service is bound to a localhost address"
template: "Port %v is exposed in a Service but listens on localhost. It will not be exposed to other pods."
args:
- name: port
@ -453,3 +453,18 @@ messages:
level: Warning
description: "Application pods should not run as user ID (UID) 1337"
template: "User ID (UID) 1337 is reserved for the sidecar proxy."
- name: "ConflictingGateways"
code: IST0145
level: Error
description: "Gateway should not have the same selector, port and matched hosts of server"
template: "Conflict with gateways %s (workload selector %s, port %s, hosts %v)."
args:
- name: gateway
type: string
- name: selector
type: string
- name: portnumber
type: string
- name: hosts
type: string

View File

@ -87,6 +87,12 @@ features:
maturity: Alpha
nextExpectedPromotion: ""
area: Traffic Management
- name: "Kubernetes Multi-Cluster Service (MCS) Discovery"
level:
checklist: features/kubernetes_mcs.md
maturity: Experimental
nextExpectedPromotion: "1.11"
area: Traffic Management
- name: "Prometheus Integration"
link: "/docs/tasks/observability/metrics/querying-metrics/"
level:
@ -263,7 +269,8 @@ features:
- name: "IPv6 Support for Kubernetes"
level:
checklist: ""
maturity: Alpha. Dual-stack IPv4 and IPv6 is not supported.
maturity: Alpha
maturityNotes: Dual-stack IPv4 and IPv6 is not supported.
nextExpectedPromotion: ""
area: Core
- name: "Distroless Base Images for Istio"