---
WARNING: THIS IS AN AUTO-GENERATED FILE, DO NOT EDIT. PLEASE MODIFY THE ORIGINAL SOURCE IN THE 'https://github.com/istio/istio' REPO
source_repo: https://github.com/istio/istio
title: istioctl
description: Istio control interface.
generator: pkg-collateral-docs
number_of_entries: 100
max_toc_level: 2
remove_toc_prefix: 'istioctl '
---
<p>Istio configuration command line utility for service operators to
debug and diagnose their Istio mesh.
</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-admin">istioctl admin</h2>
<p>A group of commands used to manage istiod configuration</p>
<pre class="language-bash"><code>istioctl admin [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl istiod [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--selector &lt;string&gt;</code></td>
<td><code>-l</code></td>
<td>label selector  (default `app=istiod`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-admin Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve information about istiod configuration.
  istioctl admin log
</code></pre>
<h2 id="istioctl-admin-log">istioctl admin log</h2>
<p>Retrieve or update logging levels of istiod components.</p>
<pre class="language-bash"><code>istioctl admin log [&lt;pod-name&gt;] [--level &lt;scope&gt;:&lt;level&gt;][--stack-trace-level &lt;scope&gt;:&lt;level&gt;]|[-r|--reset]|[--output|-o short|yaml] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl admin l [&lt;pod-name&gt;] [--level &lt;scope&gt;:&lt;level&gt;][--stack-trace-level &lt;scope&gt;:&lt;level&gt;]|[-r|--reset]|[--output|-o short|yaml] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;int&gt;</code></td>
<td></td>
<td>ControlZ port  (default `9876`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--level &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated list of output logging level for scopes in format &lt;scope&gt;:&lt;level&gt;[,&lt;scope&gt;:&lt;level&gt;,...]Possible values for &lt;level&gt;: none, error, warn, info, debug  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|short  (default `short`)</td>
</tr>
<tr>
<td><code>--reset</code></td>
<td><code>-r</code></td>
<td>Reset levels to default value. (info) </td>
</tr>
<tr>
<td><code>--selector &lt;string&gt;</code></td>
<td><code>-l</code></td>
<td>label selector  (default `app=istiod`)</td>
</tr>
<tr>
<td><code>--stack-trace-level &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated list of stack trace level  for scopes in format &lt;scope&gt;:&lt;stack-trace-level&gt;[,&lt;scope&gt;:&lt;stack-trace-level&gt;,...] Possible values for &lt;stack-trace-level&gt;: none, error, warn, info, debug  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-admin-log Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve information about istiod logging levels.
  istioctl admin log

  # Retrieve information about istiod logging levels on a specific control plane pod.
  istioctl admin l istiod-5c868d8bdd-pmvgg

  # Update levels of the specified loggers.
  istioctl admin log --level ads:debug,authorization:debug

  # Reset levels of all the loggers to default value (info).
  istioctl admin log -r

</code></pre>
<h2 id="istioctl-analyze">istioctl analyze</h2>
<p>Analyze Istio configuration and print validation messages</p>
<pre class="language-bash"><code>istioctl analyze &lt;file&gt;... [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--all-namespaces</code></td>
<td><code>-A</code></td>
<td>Analyze all namespaces </td>
</tr>
<tr>
<td><code>--color</code></td>
<td></td>
<td>Default true.  Disable with &#39;=false&#39; or set $TERM to dumb </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--failure-threshold &lt;Level&gt;</code></td>
<td></td>
<td>The severity level of analysis at which to set a non-zero exit code. Valid values: [Info Warning Error]  (default `Error`)</td>
</tr>
<tr>
<td><code>--ignore-unknown</code></td>
<td></td>
<td>Don&#39;t complain about un-parseable input documents, for cases where analyze should run only on k8s compliant inputs. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--list-analyzers</code></td>
<td><code>-L</code></td>
<td>List the analyzers available to run. Suppresses normal execution. </td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Overrides the mesh config values to use for analysis.  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of [log json yaml]  (default `log`)</td>
</tr>
<tr>
<td><code>--output-threshold &lt;Level&gt;</code></td>
<td></td>
<td>The severity level of analysis at which to display messages. Valid values: [Info Warning Error]  (default `Info`)</td>
</tr>
<tr>
<td><code>--recursive</code></td>
<td><code>-R</code></td>
<td>Process directory arguments recursively. Useful when you want to analyze related manifests organized within the same directory. </td>
</tr>
<tr>
<td><code>--suppress &lt;stringArray&gt;</code></td>
<td><code>-S</code></td>
<td>Suppress reporting a message code on a specific resource. Values are supplied in the form &lt;code&gt;=&lt;resource&gt; (e.g. &#39;--suppress &#34;IST0102=DestinationRule primary-dr.default&#34;&#39;). Can be repeated. You can include the wildcard character &#39;*&#39; to support a partial match (e.g. &#39;--suppress &#34;IST0102=DestinationRule *.default&#34; ).  (default `[]`)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--use-kube</code></td>
<td><code>-k</code></td>
<td>Use live Kubernetes cluster for analysis. Set --use-kube=false to analyze files only. </td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-analyze Examples">Examples</h3>
<pre class="language-bash"><code>  # Analyze the current live cluster
  istioctl analyze

  # Analyze the current live cluster, simulating the effect of applying additional yaml files
  istioctl analyze a.yaml b.yaml my-app-config/

  # Analyze the current live cluster, simulating the effect of applying a directory of config recursively
  istioctl analyze --recursive my-istio-config/

  # Analyze yaml files without connecting to a live cluster
  istioctl analyze --use-kube=false a.yaml b.yaml my-app-config/

  # Analyze the current live cluster and suppress PodMissingProxy for pod mypod in namespace &#39;testing&#39;.
  istioctl analyze -S &#34;IST0103=Pod mypod.testing&#34;

  # Analyze the current live cluster and suppress PodMissingProxy for all pods in namespace &#39;testing&#39;,
  # and suppress MisplacedAnnotation on deployment foobar in namespace default.
  istioctl analyze -S &#34;IST0103=Pod *.testing&#34; -S &#34;IST0107=Deployment foobar.default&#34;

  # List available analyzers
  istioctl analyze -L
</code></pre>
<h2 id="istioctl-authz">istioctl authz</h2>
<p>(authz is experimental. Use `istioctl experimental authz`)</p>
<pre class="language-bash"><code>istioctl authz [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-bug-report">istioctl bug-report</h2>
<p>bug-report selectively captures cluster information and logs into an archive to help diagnose problems.
Proxy logs can be filtered using:
  --include|--exclude ns1,ns2.../dep1,dep2.../pod1,pod2.../lbl1=val1,lbl2=val2.../ann1=val1,ann2=val2.../cntr1,cntr...
where ns=namespace, dep=deployment, lbl=label, ann=annotation, cntr=container</p>
<p>The filter spec is interpreted as &#39;must be in (ns1 OR ns2) AND (dep1 OR dep2) AND (cntr1 OR cntr2)...&#39;
The log will be included only if the container matches at least one include filter and does not match any exclude filters.
All parts of the filter are optional and can be omitted e.g. ns1//pod1 filters only for namespace ns1 and pod1.
All names except label and annotation keys support &#39;*&#39; glob matching pattern.</p>
<p>e.g.
--include ns1,ns2 (only namespaces ns1 and ns2)
--include n*//p*/l=v* (pods with name beginning with &#39;p&#39; in namespaces beginning with &#39;n&#39; and having label &#39;l&#39; with value beginning with &#39;v&#39;.)</p>
<pre class="language-bash"><code>istioctl bug-report [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--critical-errs &lt;stringSlice&gt;</code></td>
<td></td>
<td>List of comma separated glob patterns to match against log error strings. If any pattern matches an error in the log, the logs is given the highest priority for archive inclusion.  (default `[]`)</td>
</tr>
<tr>
<td><code>--dir &lt;string&gt;</code></td>
<td></td>
<td>Set a specific directory for temporary artifact storage.  (default ``)</td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td></td>
<td>Only log commands that would be run, don&#39;t fetch or write. </td>
</tr>
<tr>
<td><code>--duration &lt;duration&gt;</code></td>
<td></td>
<td>How far to go back in time from end-time for log entries to include in the archive. Default is infinity. If set, --start-time must be unset.  (default `0s`)</td>
</tr>
<tr>
<td><code>--end-time &lt;string&gt;</code></td>
<td></td>
<td>End time for the range of log entries to include in the archive. Default is now.  (default ``)</td>
</tr>
<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-node-lease,kube-public,kube-system,local-path-storage"]`)</td>
</tr>
<tr>
<td><code>--filename &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Path to a file containing configuration in YAML format. The file contents are applied over the default values and flag settings, with lists being replaced per JSON merge semantics.  (default ``)</td>
</tr>
<tr>
<td><code>--full-secrets</code></td>
<td></td>
<td>If set, secret contents are included in output. </td>
</tr>
<tr>
<td><code>--ignore-errs &lt;stringSlice&gt;</code></td>
<td></td>
<td>List of comma separated glob patterns to match against log error strings. Any error matching these patterns is ignored when calculating the log importance heuristic.  (default `[]`)</td>
</tr>
<tr>
<td><code>--include &lt;stringSlice&gt;</code></td>
<td></td>
<td>Spec for which pod&#39;s proxy logs to include in the archive. See above for format and examples.  (default `[]`)</td>
</tr>
<tr>
<td><code>--istio-namespace &lt;string&gt;</code></td>
<td></td>
<td>Namespace where Istio control plane is installed.  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--start-time &lt;string&gt;</code></td>
<td></td>
<td>Start time for the range of log entries to include in the archive. Default is the infinite past. If set, --duration must be unset.  (default ``)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>Maximum amount of time to spend fetching logs. When timeout is reached only the logs captured so far are saved to the archive.  (default `30m0s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-bug-report-version">istioctl bug-report version</h2>
<p>Prints out build version information</p>
<pre class="language-bash"><code>istioctl bug-report version [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>Name of the kubeconfig Context to use.  (default ``)</td>
</tr>
<tr>
<td><code>--critical-errs &lt;stringSlice&gt;</code></td>
<td></td>
<td>List of comma separated glob patterns to match against log error strings. If any pattern matches an error in the log, the logs is given the highest priority for archive inclusion.  (default `[]`)</td>
</tr>
<tr>
<td><code>--dir &lt;string&gt;</code></td>
<td></td>
<td>Set a specific directory for temporary artifact storage.  (default ``)</td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td></td>
<td>Only log commands that would be run, don&#39;t fetch or write. </td>
</tr>
<tr>
<td><code>--duration &lt;duration&gt;</code></td>
<td></td>
<td>How far to go back in time from end-time for log entries to include in the archive. Default is infinity. If set, --start-time must be unset.  (default `0s`)</td>
</tr>
<tr>
<td><code>--end-time &lt;string&gt;</code></td>
<td></td>
<td>End time for the range of log entries to include in the archive. Default is now.  (default ``)</td>
</tr>
<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-node-lease,kube-public,kube-system,local-path-storage"]`)</td>
</tr>
<tr>
<td><code>--filename &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Path to a file containing configuration in YAML format. The file contents are applied over the default values and flag settings, with lists being replaced per JSON merge semantics.  (default ``)</td>
</tr>
<tr>
<td><code>--full-secrets</code></td>
<td></td>
<td>If set, secret contents are included in output. </td>
</tr>
<tr>
<td><code>--ignore-errs &lt;stringSlice&gt;</code></td>
<td></td>
<td>List of comma separated glob patterns to match against log error strings. Any error matching these patterns is ignored when calculating the log importance heuristic.  (default `[]`)</td>
</tr>
<tr>
<td><code>--include &lt;stringSlice&gt;</code></td>
<td></td>
<td>Spec for which pod&#39;s proxy logs to include in the archive. See above for format and examples.  (default `[]`)</td>
</tr>
<tr>
<td><code>--istio-namespace &lt;string&gt;</code></td>
<td></td>
<td>Namespace where Istio control plane is installed.  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Path to kube config.  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>One of &#39;yaml&#39; or &#39;json&#39;.  (default ``)</td>
</tr>
<tr>
<td><code>--short</code></td>
<td><code>-s</code></td>
<td>Use --short=false to generate full version information </td>
</tr>
<tr>
<td><code>--start-time &lt;string&gt;</code></td>
<td></td>
<td>Start time for the range of log entries to include in the archive. Default is the infinite past. If set, --duration must be unset.  (default ``)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>Maximum amount of time to spend fetching logs. When timeout is reached only the logs captured so far are saved to the archive.  (default `30m0s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-completion">istioctl completion</h2>
<p>Generate the autocompletion script for istioctl for the specified shell.
See each sub-command&#39;s help for details on how to use the generated script.
</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-completion-bash">istioctl completion bash</h2>
<p>Generate the autocompletion script for the bash shell.</p>
<p>This script depends on the &#39;bash-completion&#39; package.
If it is not installed already, you can install it via your OS&#39;s package manager.</p>
<p>To load completions in your current shell session:</p>
<p>	source &lt;(istioctl completion bash)</p>
<p>To load completions for every new session, execute once:</p>
<p>#### Linux:</p>
<p>	istioctl completion bash &gt; /etc/bash_completion.d/istioctl</p>
<p>#### macOS:</p>
<p>	istioctl completion bash &gt; $(brew --prefix)/etc/bash_completion.d/istioctl</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>istioctl completion bash
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td></td>
<td>disable completion descriptions </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-completion-fish">istioctl completion fish</h2>
<p>Generate the autocompletion script for the fish shell.</p>
<p>To load completions in your current shell session:</p>
<p>	istioctl completion fish | source</p>
<p>To load completions for every new session, execute once:</p>
<p>	istioctl completion fish &gt; ~/.config/fish/completions/istioctl.fish</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>istioctl completion fish [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td></td>
<td>disable completion descriptions </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-completion-powershell">istioctl completion powershell</h2>
<p>Generate the autocompletion script for powershell.</p>
<p>To load completions in your current shell session:</p>
<p>	istioctl completion powershell | Out-String | Invoke-Expression</p>
<p>To load completions for every new session, add the output of the above command
to your powershell profile.
</p>
<pre class="language-bash"><code>istioctl completion powershell [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td></td>
<td>disable completion descriptions </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-completion-zsh">istioctl completion zsh</h2>
<p>Generate the autocompletion script for the zsh shell.</p>
<p>If shell completion is not already enabled in your environment you will need
to enable it.  You can execute the following once:</p>
<p>	echo &#34;autoload -U compinit; compinit&#34; &gt;&gt; ~/.zshrc</p>
<p>To load completions in your current shell session:</p>
<p>	source &lt;(istioctl completion zsh); compdef _istioctl istioctl</p>
<p>To load completions for every new session, execute once:</p>
<p>#### Linux:</p>
<p>	istioctl completion zsh &gt; &#34;${fpath[1]}/_istioctl&#34;</p>
<p>#### macOS:</p>
<p>	istioctl completion zsh &gt; $(brew --prefix)/share/zsh/site-functions/_istioctl</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>istioctl completion zsh [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td></td>
<td>disable completion descriptions </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-dashboard">istioctl dashboard</h2>
<p>Access to Istio web UIs</p>
<pre class="language-bash"><code>istioctl dashboard [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl dash [flags]
istioctl d [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-dashboard-controlz">istioctl dashboard controlz</h2>
<p>Open the ControlZ web UI for a pod in the Istio control plane</p>
<pre class="language-bash"><code>istioctl dashboard controlz [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;int&gt;</code></td>
<td></td>
<td>ControlZ port  (default `9876`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--selector &lt;string&gt;</code></td>
<td><code>-l</code></td>
<td>Label selector  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-controlz Examples">Examples</h3>
<pre class="language-bash"><code>  # Open ControlZ web UI for the istiod-123-456.istio-system pod
  istioctl dashboard controlz istiod-123-456.istio-system

  # Open ControlZ web UI for the istiod-56dd66799-jfdvs pod in a custom namespace
  istioctl dashboard controlz istiod-123-456 -n custom-ns

  # Open ControlZ web UI for any Istiod pod
  istioctl dashboard controlz deployment/istiod.istio-system

  # with short syntax
  istioctl dash controlz pilot-123-456.istio-system
  istioctl d controlz pilot-123-456.istio-system

</code></pre>
<h2 id="istioctl-dashboard-envoy">istioctl dashboard envoy</h2>
<p>Open the Envoy admin dashboard for a sidecar</p>
<pre class="language-bash"><code>istioctl dashboard envoy [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--selector &lt;string&gt;</code></td>
<td><code>-l</code></td>
<td>Label selector  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-envoy Examples">Examples</h3>
<pre class="language-bash"><code>  # Open Envoy dashboard for the productpage-123-456.default pod
  istioctl dashboard envoy productpage-123-456.default

  # Open Envoy dashboard for one pod under a deployment
  istioctl dashboard envoy deployment/productpage-v1

  # with short syntax
  istioctl dash envoy productpage-123-456.default
  istioctl d envoy productpage-123-456.default

</code></pre>
<h2 id="istioctl-dashboard-grafana">istioctl dashboard grafana</h2>
<p>Open Istio&#39;s Grafana dashboard</p>
<pre class="language-bash"><code>istioctl dashboard grafana [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-grafana Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard grafana

  # with short syntax
  istioctl dash grafana
  istioctl d grafana
</code></pre>
<h2 id="istioctl-dashboard-jaeger">istioctl dashboard jaeger</h2>
<p>Open Istio&#39;s Jaeger dashboard</p>
<pre class="language-bash"><code>istioctl dashboard jaeger [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-jaeger Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard jaeger

  # with short syntax
  istioctl dash jaeger
  istioctl d jaeger
</code></pre>
<h2 id="istioctl-dashboard-kiali">istioctl dashboard kiali</h2>
<p>Open Istio&#39;s Kiali dashboard</p>
<pre class="language-bash"><code>istioctl dashboard kiali [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-kiali Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard kiali

  # with short syntax
  istioctl dash kiali
  istioctl d kiali
</code></pre>
<h2 id="istioctl-dashboard-prometheus">istioctl dashboard prometheus</h2>
<p>Open Istio&#39;s Prometheus dashboard</p>
<pre class="language-bash"><code>istioctl dashboard prometheus [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-prometheus Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard prometheus

  # with short syntax
  istioctl dash prometheus
  istioctl d prometheus
</code></pre>
<h2 id="istioctl-dashboard-skywalking">istioctl dashboard skywalking</h2>
<p>Open the Istio dashboard in the SkyWalking UI</p>
<pre class="language-bash"><code>istioctl dashboard skywalking [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-skywalking Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard skywalking

  # with short syntax
  istioctl dash skywalking
  istioctl d skywalking
</code></pre>
<h2 id="istioctl-dashboard-zipkin">istioctl dashboard zipkin</h2>
<p>Open Istio&#39;s Zipkin dashboard</p>
<pre class="language-bash"><code>istioctl dashboard zipkin [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Address to listen on. Only accepts IP address or localhost as a value. When localhost is supplied, istioctl will try to bind on both 127.0.0.1 and ::1 and will fail if neither of these address are available to bind.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--browser</code></td>
<td></td>
<td>When --browser is supplied as false, istioctl dashboard will not open the browser. Default is true which means istioctl dashboard will always open a browser to view the dashboard. </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Namespace where the addon is running, if not specified, istio-system would be used  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td><code>-p</code></td>
<td>Local port to listen to  (default `0`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-dashboard-zipkin Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl dashboard zipkin

  # with short syntax
  istioctl dash zipkin
  istioctl d zipkin
</code></pre>
<h2 id="istioctl-experimental">istioctl experimental</h2>
<p>Experimental commands that may be modified or deprecated</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-add-to-mesh">istioctl experimental add-to-mesh</h2>
<p>&#39;istioctl experimental add-to-mesh&#39; restarts pods with an Istio sidecar or configures meshed pod access to external services.
Use &#39;add-to-mesh&#39; as an alternate to namespace-wide auto injection for troubleshooting compatibility.</p>
<p>The &#39;remove-from-mesh&#39; command can be used to restart with the sidecar removed.</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 [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental add [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Injection configuration filename. Cannot be used with --injectConfigMapName  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio sidecar injection, key should be &#34;config&#34;.  (default `istio-sidecar-injector`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio mesh configuration, key should be &#34;mesh&#34;  (default `istio`)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--valuesFile &lt;string&gt;</code></td>
<td></td>
<td>Injection values configuration filename.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-add-to-mesh Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart all productpage pods with an Istio sidecar
  istioctl experimental add-to-mesh service productpage

  # Restart just pods from the productpage-v1 deployment
  istioctl experimental add-to-mesh deployment productpage-v1

  # Restart just pods from the details-v1 deployment
  istioctl x add deployment details-v1

  # Control how meshed pods see an external service
  istioctl experimental add-to-mesh external-service vmhttp 172.12.23.125,172.12.23.126 \
   http:9080 tcp:8888 --labels app=test,version=v1 --annotations env=stage --serviceaccount stageAdmin
</code></pre>
<h2 id="istioctl-experimental-add-to-mesh-deployment">istioctl experimental add-to-mesh deployment</h2>
<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.15/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]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental add-to-mesh deploy &lt;deployment&gt; [flags]
istioctl experimental add-to-mesh dep &lt;deployment&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Injection configuration filename. Cannot be used with --injectConfigMapName  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio sidecar injection, key should be &#34;config&#34;.  (default `istio-sidecar-injector`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio mesh configuration, key should be &#34;mesh&#34;  (default `istio`)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--valuesFile &lt;string&gt;</code></td>
<td></td>
<td>Injection values configuration filename.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-add-to-mesh-deployment Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart pods from the productpage-v1 deployment with Istio sidecar
  istioctl experimental add-to-mesh deployment productpage-v1

  # Restart pods from the details-v1 deployment with Istio sidecar
  istioctl x add-to-mesh deploy details-v1

  # Restart pods from the ratings-v1 deployment with Istio sidecar
  istioctl x add dep ratings-v1
</code></pre>
<h2 id="istioctl-experimental-add-to-mesh-external-service">istioctl experimental add-to-mesh external-service</h2>
<p>istioctl experimental add-to-mesh external-service create a ServiceEntry and
a Service without selector for the specified external service in Istio service mesh.
The typical usage scenario is Mesh Expansion on VMs.</p>
<p>See also &#39;istioctl experimental remove-from-mesh external-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 external-service &lt;svcname&gt; &lt;ip&gt; [name1:]port1 [[name2:]port2] ... [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental add-to-mesh es &lt;svcname&gt; &lt;ip&gt; [name1:]port1 [[name2:]port2] ... [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--annotations &lt;stringSlice&gt;</code></td>
<td><code>-a</code></td>
<td>List of string annotations to apply if creating a service/endpoint; e.g. -a foo=bar,x=y  (default `[]`)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Injection configuration filename. Cannot be used with --injectConfigMapName  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio sidecar injection, key should be &#34;config&#34;.  (default `istio-sidecar-injector`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--labels &lt;stringSlice&gt;</code></td>
<td><code>-l</code></td>
<td>List of labels to apply if creating a service/endpoint; e.g. -l env=prod,vers=2  (default `[]`)</td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio mesh configuration, key should be &#34;mesh&#34;  (default `istio`)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--serviceaccount &lt;string&gt;</code></td>
<td><code>-s</code></td>
<td>Service account to link to the service  (default `default`)</td>
</tr>
<tr>
<td><code>--valuesFile &lt;string&gt;</code></td>
<td></td>
<td>Injection values configuration filename.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-add-to-mesh-external-service Examples">Examples</h3>
<pre class="language-bash"><code> # Control how meshed pods contact 172.12.23.125 and .126
  istioctl experimental add-to-mesh external-service vmhttp 172.12.23.125,172.12.23.126 \
   http:9080 tcp:8888 --labels app=test,version=v1 --annotations env=stage --serviceaccount stageAdmin
</code></pre>
<h2 id="istioctl-experimental-add-to-mesh-service">istioctl experimental add-to-mesh service</h2>
<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.15/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]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental add-to-mesh svc &lt;service&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Injection configuration filename. Cannot be used with --injectConfigMapName  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio sidecar injection, key should be &#34;config&#34;.  (default `istio-sidecar-injector`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio mesh configuration, key should be &#34;mesh&#34;  (default `istio`)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--valuesFile &lt;string&gt;</code></td>
<td></td>
<td>Injection values configuration filename.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-add-to-mesh-service Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart all productpage pods with an Istio sidecar
  istioctl experimental add-to-mesh service productpage

  # Restart all details-v1 pods with an Istio sidecar
  istioctl x add-to-mesh svc details-v1

  # Restart all ratings-v1 pods with an Istio sidecar
  istioctl x add svc ratings-v1
</code></pre>
<h2 id="istioctl-experimental-authz">istioctl experimental authz</h2>
<p></p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-authz-check">istioctl experimental authz check</h2>
<p>Check prints the AuthorizationPolicy applied to a pod by directly checking
the Envoy configuration of the pod. The command is especially useful for inspecting
the policy propagation from Istiod to Envoy and the final AuthorizationPolicy list merged
from multiple sources (mesh-level, namespace-level and workload-level).</p>
<p>The command also supports reading from a standalone config dump file with flag -f.</p>
<pre class="language-bash"><code>istioctl experimental authz check [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>The json file with Envoy config dump to be checked  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-authz-check Examples">Examples</h3>
<pre class="language-bash"><code>  # Check AuthorizationPolicy applied to pod httpbin-88ddbcfdd-nt5jb:
  istioctl x authz check httpbin-88ddbcfdd-nt5jb

  # Check AuthorizationPolicy applied to one pod under a deployment
  istioctl x authz check deployment/productpage-v1

  # Check AuthorizationPolicy from Envoy config dump file:
  istioctl x authz check -f httpbin_config_dump.json
</code></pre>
<h2 id="istioctl-experimental-config">istioctl experimental config</h2>
<p>Configure istioctl defaults</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-config Examples">Examples</h3>
<pre class="language-bash"><code>  # list configuration parameters
  istioctl config list
</code></pre>
<h2 id="istioctl-experimental-config-list">istioctl experimental config list</h2>
<p>List istio configurable defaults</p>
<pre class="language-bash"><code>istioctl experimental config list [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-create-remote-secret">istioctl experimental create-remote-secret</h2>
<p>Create a secret with credentials to allow Istio to access remote Kubernetes apiservers</p>
<pre class="language-bash"><code>istioctl experimental create-remote-secret [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--auth-plugin-config &lt;stringToString&gt;</code></td>
<td></td>
<td>Authenticator plug-in configuration. --auth-type=plugin must be set with this option  (default `[]`)</td>
</tr>
<tr>
<td><code>--auth-plugin-name &lt;string&gt;</code></td>
<td></td>
<td>Authenticator plug-in name. --auth-type=plugin must be set with this option  (default ``)</td>
</tr>
<tr>
<td><code>--auth-type &lt;RemoteSecretAuthType&gt;</code></td>
<td></td>
<td>Type of authentication to use. supported values = [bearer-token plugin]  (default `bearer-token`)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--create-service-account</code></td>
<td></td>
<td>If true, the service account needed for creating the remote secret will be created if it doesn&#39;t exist. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--name &lt;string&gt;</code></td>
<td></td>
<td>Name of the local cluster whose credentials are stored in the secret. If a name is not specified the kube-system namespace&#39;s UUID of the local cluster will be used.  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--secret-name &lt;string&gt;</code></td>
<td></td>
<td>The name of the specific secret to use from the service-account. Needed when there are multiple secrets in the service account.  (default ``)</td>
</tr>
<tr>
<td><code>--server &lt;string&gt;</code></td>
<td></td>
<td>The address and port of the Kubernetes API server.  (default ``)</td>
</tr>
<tr>
<td><code>--service-account &lt;string&gt;</code></td>
<td></td>
<td>Create a secret with this service account&#39;s credentials. Default value is &#34;istio-reader-service-account&#34; if --type is &#34;remote&#34;, &#34;istiod&#34; if --type is &#34;config&#34;.  (default ``)</td>
</tr>
<tr>
<td><code>--type &lt;SecretType&gt;</code></td>
<td></td>
<td>Type of the generated secret. supported values = [remote config]  (default `remote`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-create-remote-secret Examples">Examples</h3>
<pre class="language-bash"><code>  # Create a secret to access cluster c0&#39;s apiserver and install it in cluster c1.
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 \
    | kubectl --kubeconfig=c1.yaml apply -f -

  # Delete a secret that was previously installed in c1
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 \
    | kubectl --kubeconfig=c1.yaml delete -f -

  # Create a secret access a remote cluster with an auth plugin
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 --auth-type=plugin --auth-plugin-name=gcp \
    | kubectl --kubeconfig=c1.yaml apply -f -
</code></pre>
<h2 id="istioctl-experimental-describe">istioctl experimental describe</h2>
<p>Describe resource and related Istio configuration</p>
<pre class="language-bash"><code>istioctl experimental describe [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental des [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-describe-pod">istioctl experimental describe pod</h2>
<p>Analyzes pod, its Services, DestinationRules, and VirtualServices and reports
the configuration objects that affect that pod.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental describe pod &lt;pod&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental describe po &lt;pod&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--ignoreUnmeshed</code></td>
<td></td>
<td>Suppress warnings for unmeshed pods </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-describe-pod Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl experimental describe pod productpage-v1-c7765c886-7zzd4
</code></pre>
<h2 id="istioctl-experimental-describe-service">istioctl experimental describe service</h2>
<p>Analyzes service, pods, DestinationRules, and VirtualServices and reports
the configuration objects that affect that service.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental describe service &lt;svc&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental describe svc &lt;svc&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--ignoreUnmeshed</code></td>
<td></td>
<td>Suppress warnings for unmeshed pods </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-describe-service Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl experimental describe service productpage
</code></pre>
<h2 id="istioctl-experimental-envoy-stats">istioctl experimental envoy-stats</h2>
<p>Retrieve Envoy emitted metrics for the specified pod.</p>
<pre class="language-bash"><code>istioctl experimental envoy-stats [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental es [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|prom  (default `short`)</td>
</tr>
<tr>
<td><code>--type &lt;string&gt;</code></td>
<td><code>-t</code></td>
<td>Where to grab the stats: one of server|clusters  (default `server`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-envoy-stats Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve Envoy emitted metrics for the specified pod.
  istioctl experimental envoy-stats &lt;pod-name[.namespace]&gt;

  # Retrieve Envoy server metrics in prometheus format
  istioctl experimental envoy-stats &lt;pod-name[.namespace]&gt; --output prom

  # Retrieve Envoy server metrics in prometheus format with merged application metrics
  istioctl experimental envoy-stats &lt;pod-name[.namespace]&gt; --output prom-merged

  # Retrieve Envoy cluster metrics
  istioctl experimental envoy-stats &lt;pod-name[.namespace]&gt; --type clusters

</code></pre>
<h2 id="istioctl-experimental-injector">istioctl experimental injector</h2>
<p>List sidecar injector and sidecar versions</p>
<pre class="language-bash"><code>istioctl experimental injector [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-injector Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl experimental injector list
</code></pre>
<h2 id="istioctl-experimental-injector-list">istioctl experimental injector list</h2>
<p>List sidecar injector and sidecar versions</p>
<pre class="language-bash"><code>istioctl experimental injector list [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-injector-list Examples">Examples</h3>
<pre class="language-bash"><code>  istioctl experimental injector list
</code></pre>
<h2 id="istioctl-experimental-internal-debug">istioctl experimental internal-debug</h2>
<p>
Retrieves the debug information from Istiod or Pods in the mesh using the service account from the pod if --cert-dir is empty.
By default it will use the default serviceAccount from (istio-system) namespace if the pod is not specified.</p>
<p>
THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental internal-debug [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</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>
</tr>
<tr>
<td><code>--cert-dir &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint certificate directory  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--insecure</code></td>
<td></td>
<td>Skip server certificate and domain verification. (NOT SECURE!) </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--plaintext</code></td>
<td></td>
<td>Use plain-text HTTP/2 when connecting to server (no TLS). </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--xds-address &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint  (default ``)</td>
</tr>
<tr>
<td><code>--xds-label &lt;string&gt;</code></td>
<td></td>
<td>Istiod pod label selector  (default ``)</td>
</tr>
<tr>
<td><code>--xds-port &lt;int&gt;</code></td>
<td></td>
<td>Istiod pod port  (default `15012`)</td>
</tr>
</tbody>
</table>
<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

</code></pre>
<h2 id="istioctl-experimental-kube-uninject">istioctl experimental kube-uninject</h2>
<p>
kube-uninject is used to prevent Istio from adding a sidecar and
also provides the inverse of &#34;istioctl kube-inject -f&#34;.
</p>
<pre class="language-bash"><code>istioctl experimental kube-uninject [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--filename &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Input Kubernetes resource filename  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Modified output Kubernetes resource filename  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-kube-uninject Examples">Examples</h3>
<pre class="language-bash"><code>  # Update resources before applying.
  kubectl apply -f &lt;(istioctl experimental kube-uninject -f &lt;resource.yaml&gt;)

  # Create a persistent version of the deployment by removing Envoy sidecar.
  istioctl experimental kube-uninject -f deployment.yaml -o deployment-uninjected.yaml

  # Update an existing deployment.
  kubectl get deployment -o yaml | istioctl experimental kube-uninject -f - | kubectl apply -f -
</code></pre>
<h2 id="istioctl-experimental-metrics">istioctl experimental metrics</h2>
<p>
Prints the metrics for the specified service(s) when running in Kubernetes.</p>
<p>This command finds a Prometheus pod running in the specified istio system
namespace. It then executes a series of queries per requested workload to
find the following top-level workload metrics: total requests per second,
error rate, and request latency at p50, p90, and p99 percentiles. The
query results are printed to the console, organized by workload name.</p>
<p>All metrics returned are from server-side reports. This means that latencies
and error rates are from the perspective of the service itself and not of an
individual client (or aggregate set of clients). Rates and latencies are
calculated over a time interval of 1 minute.
</p>
<pre class="language-bash"><code>istioctl experimental metrics &lt;workload name&gt;...
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental m &lt;workload name&gt;...
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--duration &lt;duration&gt;</code></td>
<td><code>-d</code></td>
<td>Duration of query metrics, default value is 1m.  (default `1m0s`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-metrics Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve workload metrics for productpage-v1 workload
  istioctl experimental metrics productpage-v1

  # Retrieve workload metrics for various services with custom duration
  istioctl experimental metrics productpage-v1 -d 2m

  # Retrieve workload metrics for various services in the different namespaces
  istioctl experimental metrics productpage-v1.foo reviews-v1.bar ratings-v1.baz
</code></pre>
<h2 id="istioctl-experimental-precheck">istioctl experimental precheck</h2>
<p>precheck inspects a Kubernetes cluster for Istio install and upgrade requirements.</p>
<pre class="language-bash"><code>istioctl experimental precheck [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--skip-controlplane</code></td>
<td></td>
<td>skip checking the control plane </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-precheck Examples">Examples</h3>
<pre class="language-bash"><code>  # Verify that Istio can be installed or upgraded
  istioctl x precheck

  # Check only a single namespace
  istioctl x precheck --namespace default
</code></pre>
<h2 id="istioctl-experimental-proxy-status">istioctl experimental proxy-status</h2>
<p>
Retrieves last sent and last acknowledged xDS sync from Istiod to each Envoy in the mesh
</p>
<pre class="language-bash"><code>istioctl experimental proxy-status [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental ps [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--authority &lt;string&gt;</code></td>
<td></td>
<td>XDS Subject Alternative Name (for example istiod.istio-system.svc)  (default ``)</td>
</tr>
<tr>
<td><code>--cert-dir &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint certificate directory  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--insecure</code></td>
<td></td>
<td>Skip server certificate and domain verification. (NOT SECURE!) </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--plaintext</code></td>
<td></td>
<td>Use plain-text HTTP/2 when connecting to server (no TLS). </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--xds-address &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint  (default ``)</td>
</tr>
<tr>
<td><code>--xds-label &lt;string&gt;</code></td>
<td></td>
<td>Istiod pod label selector  (default ``)</td>
</tr>
<tr>
<td><code>--xds-port &lt;int&gt;</code></td>
<td></td>
<td>Istiod pod port  (default `15012`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-proxy-status Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve sync status for all Envoys in a mesh
  istioctl x proxy-status

  # Retrieve sync diff for a single Envoy and Istiod
  istioctl x proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system

  # SECURITY OPTIONS

  # Retrieve proxy status information directly from the control plane, using token security
  # (This is the usual way to get the proxy-status with an out-of-cluster control plane.)
  istioctl x ps --xds-address istio.cloudprovider.example.com:15012

  # Retrieve proxy status information via Kubernetes config, using token security
  # (This is the usual way to get the proxy-status with an in-cluster control plane.)
  istioctl x proxy-status

  # Retrieve proxy status 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 ps --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs

  # Retrieve proxy status 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 ps --xds-label istio.io/rev=default

</code></pre>
<h2 id="istioctl-experimental-remote-clusters">istioctl experimental remote-clusters</h2>
<p>Lists the remote clusters each istiod instance is connected to.</p>
<pre class="language-bash"><code>istioctl experimental remote-clusters [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-remove-from-mesh">istioctl experimental remove-from-mesh</h2>
<p>&#39;istioctl experimental remove-from-mesh&#39; restarts pods without an Istio sidecar or removes external service access configuration.
Use &#39;remove-from-mesh&#39; to quickly test uninjected behavior as part of compatibility troubleshooting.
The &#39;add-to-mesh&#39; command can be used to add or restore the sidecar.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental remove-from-mesh [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental rm [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-remove-from-mesh Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart all productpage pods without an Istio sidecar
  istioctl experimental remove-from-mesh service productpage

  # Restart all details-v1 pods without an Istio sidecar
  istioctl x rm service details-v1

  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm deploy ratings-v1
</code></pre>
<h2 id="istioctl-experimental-remove-from-mesh-deployment">istioctl experimental remove-from-mesh deployment</h2>
<p>&#39;istioctl experimental remove-from-mesh deployment&#39; restarts pods with the Istio sidecar un-injected.
&#39;remove-from-mesh&#39; is a compatibility troubleshooting tool.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental remove-from-mesh deployment &lt;deployment&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental remove-from-mesh deploy &lt;deployment&gt; [flags]
istioctl experimental remove-from-mesh dep &lt;deployment&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-remove-from-mesh-deployment Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart all productpage-v1 pods without an Istio sidecar
  istioctl experimental remove-from-mesh deployment productpage-v1

  # Restart all details-v1 pods without an Istio sidecar
  istioctl x remove-from-mesh deploy details-v1

  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm dep ratings-v1
</code></pre>
<h2 id="istioctl-experimental-remove-from-mesh-external-service">istioctl experimental remove-from-mesh external-service</h2>
<p>&#39;istioctl experimental remove-from-mesh external-service&#39; removes the ServiceEntry and
the Kubernetes Service for the specified external service (e.g. services running on a VM) from Istio service mesh.
The typical usage scenario is Mesh Expansion on VMs.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental remove-from-mesh external-service &lt;svcname&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental remove-from-mesh es &lt;svcname&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-remove-from-mesh-external-service Examples">Examples</h3>
<pre class="language-bash"><code>  # Remove &#34;vmhttp&#34; service entry rules
  istioctl experimental remove-from-mesh external-service vmhttp

  # Remove &#34;vmhttp&#34; service entry rules
  istioctl x remove-from-mesh es vmhttp

  # Remove &#34;vmhttp&#34; service entry rules
  istioctl x rm es vmhttp
</code></pre>
<h2 id="istioctl-experimental-remove-from-mesh-service">istioctl experimental remove-from-mesh service</h2>
<p>&#39;istioctl experimental remove-from-mesh service&#39; restarts pods with the Istio sidecar un-injected.
&#39;remove-from-mesh&#39; is a compatibility troubleshooting tool.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl experimental remove-from-mesh service &lt;service&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental remove-from-mesh svc &lt;service&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-remove-from-mesh-service Examples">Examples</h3>
<pre class="language-bash"><code>  # Restart all productpage pods without an Istio sidecar
  istioctl experimental remove-from-mesh service productpage

  # Restart all details-v1 pods without an Istio sidecar
  istioctl x remove-from-mesh svc details-v1

  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm svc ratings-v1
</code></pre>
<h2 id="istioctl-experimental-revision">istioctl experimental revision</h2>
<p>The revision command provides a revision centric view of istio deployments. It provides insight into IstioOperator CRs defining the revision, istiod and gateway pods which are part of deployment of a particular revision.</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-revision-describe">istioctl experimental revision describe</h2>
<p>Show information about a revision, including customizations, istiod version and which pods/gateways are using it.</p>
<pre class="language-bash"><code>istioctl experimental revision describe [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-describe Examples">Examples</h3>
<pre class="language-bash"><code>  # View the details of a revision named &#39;canary&#39;
  istioctl x revision describe canary

  # View the details of a revision named &#39;canary&#39; and also the pods
  # under that particular revision
  istioctl x revision describe canary -v

  # Get details about a revision in json format (default format is human-friendly table format)
  istioctl x revision describe canary -v -o json

</code></pre>
<h2 id="istioctl-experimental-revision-list">istioctl experimental revision list</h2>
<p>Show list of control plane and gateway revisions that are currently installed in cluster</p>
<pre class="language-bash"><code>istioctl experimental revision list [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-list Examples">Examples</h3>
<pre class="language-bash"><code>  # View summary of revisions installed in the current cluster
  # which can be overridden with --context parameter.
  istioctl x revision list

  # View list of revisions including customizations, istiod and gateway pods
  istioctl x revision list -v

</code></pre>
<h2 id="istioctl-experimental-revision-tag">istioctl experimental revision tag</h2>
<p>Command group used to interact with revision tags. Revision tags allow for the creation of mutable aliases
referring to control plane revisions for sidecar injection.</p>
<p>With revision tags, rather than relabeling a namespace from &#34;istio.io/rev=revision-a&#34; to &#34;istio.io/rev=revision-b&#34; to
change which control plane revision handles injection, it&#39;s possible to create a revision tag &#34;prod&#34; and label our
namespace &#34;istio.io/rev=prod&#34;. The &#34;prod&#34; revision tag could point to &#34;1-7-6&#34; initially and then be changed to point to &#34;1-8-1&#34;
at some later point.</p>
<p>This allows operators to change which Istio control plane revision should handle injection for a namespace or set of namespaces
without manual relabeling of the &#34;istio.io/rev&#34; tag.
</p>
<pre class="language-bash"><code>istioctl experimental revision tag [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-experimental-revision-tag-generate">istioctl experimental revision tag generate</h2>
<p>Create a revision tag and output to the command&#39;s stdout. Tag an Istio control plane revision for use with namespace istio.io/rev
injection labels.</p>
<pre class="language-bash"><code>istioctl experimental revision tag generate &lt;revision-tag&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--auto-inject-namespaces</code></td>
<td></td>
<td>If set to true, the sidecars should be automatically injected into all namespaces by default </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--overwrite</code></td>
<td></td>
<td>If true, allow revision tags to be overwritten, otherwise reject revision tag updates that
overwrite existing revision tags. </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision to reference from a given revision tag  (default ``)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--webhook-name &lt;string&gt;</code></td>
<td></td>
<td>Name to use for a revision tag&#39;s mutating webhook configuration.  (default ``)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-tag-generate Examples">Examples</h3>
<pre class="language-bash"><code> # Create a revision tag from the &#34;1-8-0&#34; revision
 istioctl tag generate prod --revision 1-8-0 &gt; tag.yaml

 # Apply the tag to cluster
 kubectl apply -f tag.yaml

 # Point namespace &#34;test-ns&#34; at the revision pointed to by the &#34;prod&#34; revision tag
 kubectl label ns test-ns istio.io/rev=prod

 # Rollout namespace &#34;test-ns&#34; to update workloads to the &#34;1-8-0&#34; revision
 kubectl rollout restart deployments -n test-ns

</code></pre>
<h2 id="istioctl-experimental-revision-tag-list">istioctl experimental revision tag list</h2>
<p>List existing revision tags</p>
<pre class="language-bash"><code>istioctl experimental revision tag list [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental revision tag show [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-tag-list Examples">Examples</h3>
<pre class="language-bash"><code>istioctl tag list
</code></pre>
<h2 id="istioctl-experimental-revision-tag-remove">istioctl experimental revision tag remove</h2>
<p>Remove Istio control plane revision tag.</p>
<p>Removing a revision tag should be done with care. Removing a revision tag will disrupt sidecar injection in namespaces
that reference the tag in an &#34;istio.io/rev&#34; label. Verify that there are no remaining namespaces referencing a
revision tag before removing using the &#34;istioctl tag list&#34; command.
</p>
<pre class="language-bash"><code>istioctl experimental revision tag remove &lt;revision-tag&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl experimental revision tag delete &lt;revision-tag&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-tag-remove Examples">Examples</h3>
<pre class="language-bash"><code> # Remove the revision tag &#34;prod&#34;
	istioctl tag remove prod

</code></pre>
<h2 id="istioctl-experimental-revision-tag-set">istioctl experimental revision tag set</h2>
<p>Create or modify revision tags. Tag an Istio control plane revision for use with namespace istio.io/rev
injection labels.</p>
<pre class="language-bash"><code>istioctl experimental revision tag set &lt;revision-tag&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--auto-inject-namespaces</code></td>
<td></td>
<td>If set to true, the sidecars should be automatically injected into all namespaces by default </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format for revision description (available formats: table,json)  (default `table`)</td>
</tr>
<tr>
<td><code>--overwrite</code></td>
<td></td>
<td>If true, allow revision tags to be overwritten, otherwise reject revision tag updates that
overwrite existing revision tags. </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision to reference from a given revision tag  (default ``)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Enable verbose output </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--webhook-name &lt;string&gt;</code></td>
<td></td>
<td>Name to use for a revision tag&#39;s mutating webhook configuration.  (default ``)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-revision-tag-set Examples">Examples</h3>
<pre class="language-bash"><code> # Create a revision tag from the &#34;1-8-0&#34; revision
 istioctl tag set prod --revision 1-8-0

 # Point namespace &#34;test-ns&#34; at the revision pointed to by the &#34;prod&#34; revision tag
 kubectl label ns test-ns istio.io/rev=prod

 # Change the revision tag to reference the &#34;1-8-1&#34; revision
 istioctl tag set prod --revision 1-8-1 --overwrite

 # Make revision &#34;1-8-1&#34; the default revision, both resulting in that revision handling injection for &#34;istio-injection=enabled&#34;
 # and validating resources cluster-wide
 istioctl tag set default --revision 1-8-1

 # Rollout namespace &#34;test-ns&#34; to update workloads to the &#34;1-8-1&#34; revision
 kubectl rollout restart deployments -n test-ns

</code></pre>
<h2 id="istioctl-experimental-uninstall">istioctl experimental uninstall</h2>
<p>The uninstall command uninstalls Istio from a cluster</p>
<pre class="language-bash"><code>istioctl experimental uninstall [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>
</tr>
<tr>
<td><code>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--purge</code></td>
<td></td>
<td>Delete all Istio related sources for all versions </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target control plane revision for the command.  (default ``)</td>
</tr>
<tr>
<td><code>--set &lt;stringArray&gt;</code></td>
<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.15/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec  (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Verbose output. </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-uninstall Examples">Examples</h3>
<pre class="language-bash"><code>  # Uninstall a single control plane by revision
  istioctl x uninstall --revision foo

  # Uninstall a single control plane by iop file
  istioctl x uninstall -f iop.yaml
  
  # Uninstall all control planes and shared resources
  istioctl x uninstall --purge
</code></pre>
<h2 id="istioctl-experimental-version">istioctl experimental version</h2>
<p>Prints out build version information</p>
<pre class="language-bash"><code>istioctl experimental version [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--authority &lt;string&gt;</code></td>
<td></td>
<td>XDS Subject Alternative Name (for example istiod.istio-system.svc)  (default ``)</td>
</tr>
<tr>
<td><code>--cert-dir &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint certificate directory  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--insecure</code></td>
<td></td>
<td>Skip server certificate and domain verification. (NOT SECURE!) </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>One of &#39;yaml&#39; or &#39;json&#39;.  (default ``)</td>
</tr>
<tr>
<td><code>--plaintext</code></td>
<td></td>
<td>Use plain-text HTTP/2 when connecting to server (no TLS). </td>
</tr>
<tr>
<td><code>--remote</code></td>
<td></td>
<td>Use --remote=false to suppress control plane check </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--short</code></td>
<td><code>-s</code></td>
<td>Use --short=false to generate full version information </td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--xds-address &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint  (default ``)</td>
</tr>
<tr>
<td><code>--xds-label &lt;string&gt;</code></td>
<td></td>
<td>Istiod pod label selector  (default ``)</td>
</tr>
<tr>
<td><code>--xds-port &lt;int&gt;</code></td>
<td></td>
<td>Istiod pod port  (default `15012`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-version Examples">Examples</h3>
<pre class="language-bash"><code># Retrieve version information directly from the control plane, using token security
# (This is the usual way to get the control plane version with an out-of-cluster control plane.)
istioctl x version --xds-address istio.cloudprovider.example.com:15012

# Retrieve version information via Kubernetes config, using token security
# (This is the usual way to get the control plane version with an in-cluster control plane.)
istioctl x version

# Retrieve version 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 version --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs

# Retrieve version 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 version --xds-label istio.io/rev=default

</code></pre>
<h2 id="istioctl-experimental-wait">istioctl experimental wait</h2>
<p>Waits for the specified condition to be true of an Istio resource.</p>
<pre class="language-bash"><code>istioctl experimental wait [flags] &lt;type&gt; &lt;name&gt;[.&lt;namespace&gt;]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--for &lt;string&gt;</code></td>
<td></td>
<td>Wait condition, must be &#39;distribution&#39; or &#39;delete&#39;  (default `distribution`)</td>
</tr>
<tr>
<td><code>--generation &lt;string&gt;</code></td>
<td></td>
<td>Wait for a specific generation of config to become current, rather than using whatever is latest in Kubernetes  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--threshold &lt;float32&gt;</code></td>
<td></td>
<td>The ratio of distribution required for success  (default `1`)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-wait Examples">Examples</h3>
<pre class="language-bash"><code>  # Wait until the bookinfo virtual service has been distributed to all proxies in the mesh
  istioctl experimental wait --for=distribution virtualservice bookinfo.default

  # Wait until 99% of the proxies receive the distribution, timing out after 5 minutes
  istioctl experimental wait --for=distribution --threshold=.99 --timeout=300s virtualservice bookinfo.default

</code></pre>
<h2 id="istioctl-experimental-workload">istioctl experimental workload</h2>
<p>Commands to assist in configuring and deploying workloads running on VMs and other non-Kubernetes environments</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload Examples">Examples</h3>
<pre class="language-bash"><code>  # workload group yaml generation
  workload group create

  # workload entry configuration generation
  workload entry configure
</code></pre>
<h2 id="istioctl-experimental-workload-entry">istioctl experimental workload entry</h2>
<p>Commands dealing with WorkloadEntry resources</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload-entry Examples">Examples</h3>
<pre class="language-bash"><code>entry configure -f workloadgroup.yaml -o outputDir
</code></pre>
<h2 id="istioctl-experimental-workload-entry-configure">istioctl experimental workload entry configure</h2>
<p>Generates all the required configuration files for workload instance on a VM or non-Kubernetes environment from a WorkloadGroup artifact.
This includes a MeshConfig resource, the cluster.env file, and necessary certificates and security tokens.
Configure requires either the WorkloadGroup artifact path or its location on the API server.</p>
<pre class="language-bash"><code>istioctl experimental workload entry configure [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--autoregister</code></td>
<td></td>
<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 ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--externalIP &lt;string&gt;</code></td>
<td></td>
<td>External IP address of the workload  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>filename of the WorkloadGroup artifact. Leave this field empty if using the API server  (default ``)</td>
</tr>
<tr>
<td><code>--ingressIP &lt;string&gt;</code></td>
<td></td>
<td>IP address of the ingress gateway  (default ``)</td>
</tr>
<tr>
<td><code>--ingressService &lt;string&gt;</code></td>
<td></td>
<td>Name of the Service to be used as the ingress gateway, in the format &lt;service&gt;.&lt;namespace&gt;. If no namespace is provided, the default istio-system namespace will be used.  (default `istio-eastwestgateway`)</td>
</tr>
<tr>
<td><code>--internalIP &lt;string&gt;</code></td>
<td></td>
<td>Internal IP address of the workload  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--name &lt;string&gt;</code></td>
<td></td>
<td>The name of the workload group  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output directory for generated files  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--tokenDuration &lt;int&gt;</code></td>
<td></td>
<td>The token duration in seconds (default: 1 hour)  (default `3600`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload-entry-configure Examples">Examples</h3>
<pre class="language-bash"><code>  # configure example using a local WorkloadGroup artifact
  configure -f workloadgroup.yaml -o config

  # configure example using the API server
  configure --name foo --namespace bar -o config
</code></pre>
<h2 id="istioctl-experimental-workload-group">istioctl experimental workload group</h2>
<p>Commands dealing with WorkloadGroup resources</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload-group Examples">Examples</h3>
<pre class="language-bash"><code>group create --name foo --namespace bar --labels app=foobar
</code></pre>
<h2 id="istioctl-experimental-workload-group-create">istioctl experimental workload group create</h2>
<p>Creates a WorkloadGroup resource that provides a template for associated WorkloadEntries.
The default output is serialized YAML, which can be piped into &#39;kubectl apply -f -&#39; to send the artifact to the API Server.</p>
<pre class="language-bash"><code>istioctl experimental workload group create [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--annotations &lt;stringSlice&gt;</code></td>
<td><code>-a</code></td>
<td>The annotations to apply to the workload instances  (default `[]`)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--labels &lt;stringSlice&gt;</code></td>
<td><code>-l</code></td>
<td>The labels to apply to the workload instances; e.g. -l env=prod,vers=2  (default `[]`)</td>
</tr>
<tr>
<td><code>--name &lt;string&gt;</code></td>
<td></td>
<td>The name of the workload group  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--ports &lt;stringSlice&gt;</code></td>
<td><code>-p</code></td>
<td>The incoming ports exposed by the workload instance  (default `[]`)</td>
</tr>
<tr>
<td><code>--serviceAccount &lt;string&gt;</code></td>
<td><code>-s</code></td>
<td>The service identity to associate with the workload instances  (default `default`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-experimental-workload-group-create Examples">Examples</h3>
<pre class="language-bash"><code>create --name foo --namespace bar --labels app=foo,bar=baz --ports grpc=3550,http=8080 --annotations annotation=foobar --serviceAccount sa
</code></pre>
<h2 id="istioctl-install">istioctl install</h2>
<p>The install command generates an Istio install manifest and applies it to a cluster.</p>
<pre class="language-bash"><code>istioctl install [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl apply [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default `[]`)</td>
</tr>
<tr>
<td><code>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--readiness-timeout &lt;duration&gt;</code></td>
<td></td>
<td>Maximum time to wait for Istio resources in each component to be ready.  (default `5m0s`)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target control plane revision for the command.  (default ``)</td>
</tr>
<tr>
<td><code>--set &lt;stringArray&gt;</code></td>
<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.15/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec  (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verify</code></td>
<td></td>
<td>Verify the Istio control plane after installation/in-place upgrade </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-install Examples">Examples</h3>
<pre class="language-bash"><code>  # Apply a default Istio installation
  istioctl install

  # Enable Tracing
  istioctl install --set meshConfig.enableTracing=true

  # Generate the demo profile and don&#39;t wait for confirmation
  istioctl install --set profile=demo --skip-confirmation

  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl install --set &#34;values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default&#34;

  # For setting boolean-string option, it should be enclosed quotes and escaped with a backslash (\).
  istioctl install --set meshConfig.defaultConfig.proxyMetadata.PROXY_XDS_VIA_AGENT=\&#34;false\&#34;

</code></pre>
<h2 id="istioctl-kube-inject">istioctl kube-inject</h2>
<p>
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. 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>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--authority &lt;string&gt;</code></td>
<td></td>
<td>XDS Subject Alternative Name (for example istiod.istio-system.svc)  (default ``)</td>
</tr>
<tr>
<td><code>--cert-dir &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint certificate directory  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--filename &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Input Kubernetes resource filename  (default ``)</td>
</tr>
<tr>
<td><code>--injectConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Injection configuration filename. Cannot be used with --injectConfigMapName  (default ``)</td>
</tr>
<tr>
<td><code>--insecure</code></td>
<td></td>
<td>Skip server certificate and domain verification. (NOT SECURE!) </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigFile &lt;string&gt;</code></td>
<td></td>
<td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set  (default ``)</td>
</tr>
<tr>
<td><code>--meshConfigMapName &lt;string&gt;</code></td>
<td></td>
<td>ConfigMap name for Istio mesh configuration, key should be &#34;mesh&#34;  (default `istio`)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--operatorFileName &lt;string&gt;</code></td>
<td></td>
<td>Path to file containing IstioOperator custom resources. If configs from files like meshConfigFile, valuesFile are provided, they will be overridden by iop config values.  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Modified output Kubernetes resource filename  (default ``)</td>
</tr>
<tr>
<td><code>--plaintext</code></td>
<td></td>
<td>Use plain-text HTTP/2 when connecting to server (no TLS). </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--timeout &lt;duration&gt;</code></td>
<td></td>
<td>The duration to wait before failing  (default `30s`)</td>
</tr>
<tr>
<td><code>--valuesFile &lt;string&gt;</code></td>
<td></td>
<td>Injection values configuration filename.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--webhookConfig &lt;string&gt;</code></td>
<td></td>
<td>MutatingWebhookConfiguration name for Istio  (default `istio-sidecar-injector`)</td>
</tr>
<tr>
<td><code>--xds-address &lt;string&gt;</code></td>
<td></td>
<td>XDS Endpoint  (default ``)</td>
</tr>
<tr>
<td><code>--xds-label &lt;string&gt;</code></td>
<td></td>
<td>Istiod pod label selector  (default ``)</td>
</tr>
<tr>
<td><code>--xds-port &lt;int&gt;</code></td>
<td></td>
<td>Istiod pod port  (default `15012`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-kube-inject Examples">Examples</h3>
<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 Istio sidecar injected.
  istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml

  # Update an existing deployment.
  kubectl get deployment -o yaml | istioctl kube-inject -f - | kubectl apply -f -

  # Capture cluster configuration for later use with kube-inject
  kubectl -n istio-system get cm istio-sidecar-injector  -o jsonpath=&#34;{.data.config}&#34; &gt; /tmp/inj-template.tmpl
  kubectl -n istio-system get cm istio -o jsonpath=&#34;{.data.mesh}&#34; &gt; /tmp/mesh.yaml
  kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath=&#34;{.data.values}&#34; &gt; /tmp/values.json

  # Use kube-inject based on captured configuration
  istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml \
    --injectConfigFile /tmp/inj-template.tmpl \
    --meshConfigFile /tmp/mesh.yaml \
    --valuesFile /tmp/values.json

</code></pre>
<h2 id="istioctl-manifest">istioctl manifest</h2>
<p>The manifest command generates and diffs Istio manifests.</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-manifest-diff">istioctl manifest diff</h2>
<p>The diff subcommand compares manifests from two files or directories. The output is a list of
changed paths with the value changes shown as OLD-VALUE -&gt; NEW-VALUE.
List order changes are shown as [OLD-INDEX-&gt;NEW-INDEX], with ? used where a list item is added or
removed.</p>
<pre class="language-bash"><code>istioctl manifest diff &lt;file|dir&gt; &lt;file|dir&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--directory</code></td>
<td><code>-r</code></td>
<td>Compare directory. </td>
</tr>
<tr>
<td><code>--dry-run</code></td>
<td></td>
<td>Console/log output only, make no changes. </td>
</tr>
<tr>
<td><code>--ignore &lt;string&gt;</code></td>
<td></td>
<td>Ignore all listed items during comparison, using the same list format as selectResources.  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--rename &lt;string&gt;</code></td>
<td></td>
<td>Rename resources before comparison.
The format of each renaming pair is A-&gt;B, all renaming pairs are comma separated.
e.g. Service:*:istiod-&gt;Service:*:istio-control - rename istiod service into istio-control  (default ``)</td>
</tr>
<tr>
<td><code>--select &lt;string&gt;</code></td>
<td></td>
<td>Constrain the list of resources to compare to only the ones in this list, ignoring all others.
The format of each list item is &#34;::&#34; and the items are comma separated. The &#34;*&#34; character represents wildcard selection.
e.g.
    Deployment:istio-system:* - compare all deployments in istio-system namespace
    Service:*:istiod - compare Services called &#34;istiod&#34; in all namespaces  (default `::`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td><code>-v</code></td>
<td>Verbose output. </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-manifest-generate">istioctl manifest generate</h2>
<p>The generate subcommand generates an Istio install manifest and outputs to the console by default.</p>
<pre class="language-bash"><code>istioctl manifest generate [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--component &lt;stringSlice&gt;</code></td>
<td></td>
<td>Specify which component to generate manifests for.  (default `[]`)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default `[]`)</td>
</tr>
<tr>
<td><code>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Manifest output directory path.  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target control plane revision for the command.  (default ``)</td>
</tr>
<tr>
<td><code>--set &lt;stringArray&gt;</code></td>
<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.15/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec  (default `[]`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-manifest-generate Examples">Examples</h3>
<pre class="language-bash"><code>  # Generate a default Istio installation
  istioctl manifest generate

  # Enable Tracing
  istioctl manifest generate --set meshConfig.enableTracing=true

  # Generate the demo profile
  istioctl manifest generate --set profile=demo

  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl manifest generate --set &#34;values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default&#34;

  # For setting boolean-string option, it should be enclosed quotes and escaped with a backslash (\).
  istioctl manifest generate --set meshConfig.defaultConfig.proxyMetadata.PROXY_XDS_VIA_AGENT=\&#34;false\&#34;

</code></pre>
<h2 id="istioctl-manifest-install">istioctl manifest install</h2>
<p>The install command generates an Istio install manifest and applies it to a cluster.</p>
<pre class="language-bash"><code>istioctl manifest install [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl manifest apply [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default `[]`)</td>
</tr>
<tr>
<td><code>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--readiness-timeout &lt;duration&gt;</code></td>
<td></td>
<td>Maximum time to wait for Istio resources in each component to be ready.  (default `5m0s`)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target control plane revision for the command.  (default ``)</td>
</tr>
<tr>
<td><code>--set &lt;stringArray&gt;</code></td>
<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.15/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec  (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verify</code></td>
<td></td>
<td>Verify the Istio control plane after installation/in-place upgrade </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-manifest-install Examples">Examples</h3>
<pre class="language-bash"><code>  # Apply a default Istio installation
  istioctl install

  # Enable Tracing
  istioctl install --set meshConfig.enableTracing=true

  # Generate the demo profile and don&#39;t wait for confirmation
  istioctl install --set profile=demo --skip-confirmation

  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl install --set &#34;values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default&#34;

  # For setting boolean-string option, it should be enclosed quotes and escaped with a backslash (\).
  istioctl install --set meshConfig.defaultConfig.proxyMetadata.PROXY_XDS_VIA_AGENT=\&#34;false\&#34;

</code></pre>
<h2 id="istioctl-operator">istioctl operator</h2>
<p>The operator command installs, dumps, removes and shows the status of the operator controller.</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-operator-dump">istioctl operator dump</h2>
<p>The dump subcommand dumps the Istio operator controller manifest.</p>
<pre class="language-bash"><code>istioctl operator dump [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--hub &lt;string&gt;</code></td>
<td></td>
<td>The hub for the operator controller image.  (default `unknown`)</td>
</tr>
<tr>
<td><code>--imagePullSecrets &lt;stringSlice&gt;</code></td>
<td></td>
<td>The imagePullSecrets are used to pull the operator image from the private registry,
could be secret list separated by comma, eg. &#39;--imagePullSecrets imagePullSecret1,imagePullSecret2&#39;  (default `[]`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--operatorNamespace &lt;string&gt;</code></td>
<td></td>
<td>The namespace the operator controller is installed into.  (default `istio-operator`)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml  (default `yaml`)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target revision for the operator.  (default ``)</td>
</tr>
<tr>
<td><code>--tag &lt;string&gt;</code></td>
<td></td>
<td>The tag for the operator controller image.  (default `unknown`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--watchedNamespaces &lt;string&gt;</code></td>
<td></td>
<td>The namespaces the operator controller watches, could be namespace list separated by comma, eg. &#39;ns1,ns2&#39;  (default `istio-system`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-operator-init">istioctl operator init</h2>
<p>The init subcommand installs the Istio operator controller in the cluster.</p>
<pre class="language-bash"><code>istioctl operator init [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default ``)</td>
</tr>
<tr>
<td><code>--hub &lt;string&gt;</code></td>
<td></td>
<td>The hub for the operator controller image.  (default `unknown`)</td>
</tr>
<tr>
<td><code>--imagePullSecrets &lt;stringSlice&gt;</code></td>
<td></td>
<td>The imagePullSecrets are used to pull the operator image from the private registry,
could be secret list separated by comma, eg. &#39;--imagePullSecrets imagePullSecret1,imagePullSecret2&#39;  (default `[]`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--operatorNamespace &lt;string&gt;</code></td>
<td></td>
<td>The namespace the operator controller is installed into.  (default `istio-operator`)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target revision for the operator.  (default ``)</td>
</tr>
<tr>
<td><code>--tag &lt;string&gt;</code></td>
<td></td>
<td>The tag for the operator controller image.  (default `unknown`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--watchedNamespaces &lt;string&gt;</code></td>
<td></td>
<td>The namespaces the operator controller watches, could be namespace list separated by comma, eg. &#39;ns1,ns2&#39;  (default `istio-system`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-operator-remove">istioctl operator remove</h2>
<p>The remove subcommand removes the Istio operator controller from the cluster.</p>
<pre class="language-bash"><code>istioctl operator remove [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--operatorNamespace &lt;string&gt;</code></td>
<td></td>
<td>The namespace the operator controller is installed into.  (default `istio-operator`)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Target revision for the operator.  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-options">istioctl options</h2>
<p>Displays istioctl global options</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-profile">istioctl profile</h2>
<p>The profile command lists, dumps or diffs Istio configuration profiles.</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-profile Examples">Examples</h3>
<pre class="language-bash"><code>istioctl profile list
istioctl install --set profile=demo  # Use a profile from the list
</code></pre>
<h2 id="istioctl-profile-diff">istioctl profile diff</h2>
<p>The diff subcommand displays the differences between two Istio configuration profiles.</p>
<pre class="language-bash"><code>istioctl profile diff &lt;profile|file1.yaml&gt; &lt;profile|file2.yaml&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-profile-diff Examples">Examples</h3>
<pre class="language-bash"><code>  # Profile diff by providing yaml files
  istioctl profile diff manifests/profiles/default.yaml manifests/profiles/demo.yaml

  # Profile diff by providing a profile name
  istioctl profile diff default demo
</code></pre>
<h2 id="istioctl-profile-dump">istioctl profile dump</h2>
<p>The dump subcommand dumps the values in an Istio configuration profile.</p>
<pre class="language-bash"><code>istioctl profile dump [&lt;profile&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--config-path &lt;string&gt;</code></td>
<td><code>-p</code></td>
<td>The path the root of the configuration subtree to dump e.g. components.pilot. By default, dump whole tree  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default `[]`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|flags  (default `yaml`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-profile-list">istioctl profile list</h2>
<p>The list subcommand lists the available Istio configuration profiles.</p>
<pre class="language-bash"><code>istioctl profile list [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-proxy-config">istioctl proxy-config</h2>
<p>A group of commands used to retrieve information about proxy configuration from the Envoy config dump</p>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve information about proxy configuration from an Envoy instance.
  istioctl proxy-config &lt;clusters|listeners|routes|endpoints|bootstrap|log|secret&gt; &lt;pod-name[.namespace]&gt;
</code></pre>
<h2 id="istioctl-proxy-config-all">istioctl proxy-config all</h2>
<p>Retrieve information about all configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config all [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config a [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by address field  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--direction &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by Direction field  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump file  (default ``)</td>
</tr>
<tr>
<td><code>--fqdn &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by substring of Service FQDN field  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--name &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by route name field  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td></td>
<td>Filter clusters and listeners by Port field  (default `0`)</td>
</tr>
<tr>
<td><code>--subset &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by substring of Subset field  (default ``)</td>
</tr>
<tr>
<td><code>--type &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by type field  (default ``)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td></td>
<td>Output more information </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-all Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve summary about all configuration for a given pod from Envoy.
  istioctl proxy-config all &lt;pod-name[.namespace]&gt;

  # Retrieve full cluster dump as JSON
  istioctl proxy-config all &lt;pod-name[.namespace]&gt; -o json

  # Retrieve full cluster dump with short syntax
  istioctl pc a &lt;pod-name[.namespace]&gt;

  # Retrieve cluster summary without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config all --file envoy-config.json

</code></pre>
<h2 id="istioctl-proxy-config-bootstrap">istioctl proxy-config bootstrap</h2>
<p>Retrieve information about bootstrap configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config bootstrap [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config b [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-bootstrap Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve full bootstrap configuration for a given pod from Envoy.
  istioctl proxy-config bootstrap &lt;pod-name[.namespace]&gt;

  # Retrieve full bootstrap without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config bootstrap --file envoy-config.json

  # Show a human-readable Istio and Envoy version summary
  istioctl proxy-config bootstrap -o short

</code></pre>
<h2 id="istioctl-proxy-config-cluster">istioctl proxy-config cluster</h2>
<p>Retrieve information about cluster configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config cluster [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config clusters [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
istioctl proxy-config c [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--direction &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by Direction field  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--fqdn &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by substring of Service FQDN field  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td></td>
<td>Filter clusters by Port field  (default `0`)</td>
</tr>
<tr>
<td><code>--subset &lt;string&gt;</code></td>
<td></td>
<td>Filter clusters by substring of Subset field  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-cluster Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve summary about cluster configuration for a given pod from Envoy.
  istioctl proxy-config clusters &lt;pod-name[.namespace]&gt;

  # Retrieve cluster summary for clusters with port 9080.
  istioctl proxy-config clusters &lt;pod-name[.namespace]&gt; --port 9080

  # Retrieve full cluster dump for clusters that are inbound with a FQDN of details.default.svc.cluster.local.
  istioctl proxy-config clusters &lt;pod-name[.namespace]&gt; --fqdn details.default.svc.cluster.local --direction inbound -o json

  # Retrieve cluster summary without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config clusters --file envoy-config.json

</code></pre>
<h2 id="istioctl-proxy-config-endpoint">istioctl proxy-config endpoint</h2>
<p>Retrieve information about endpoint configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config endpoint [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config endpoints [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
istioctl proxy-config ep [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Filter endpoints by address field  (default ``)</td>
</tr>
<tr>
<td><code>--cluster &lt;string&gt;</code></td>
<td></td>
<td>Filter endpoints by cluster name field  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td></td>
<td>Filter endpoints by Port field  (default `0`)</td>
</tr>
<tr>
<td><code>--status &lt;string&gt;</code></td>
<td></td>
<td>Filter endpoints by status field  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-endpoint Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve full endpoint configuration for a given pod from Envoy.
  istioctl proxy-config endpoint &lt;pod-name[.namespace]&gt;

  # Retrieve endpoint summary for endpoint with port 9080.
  istioctl proxy-config endpoint &lt;pod-name[.namespace]&gt; --port 9080

  # Retrieve full endpoint with a address (172.17.0.2).
  istioctl proxy-config endpoint &lt;pod-name[.namespace]&gt; --address 172.17.0.2 -o json

  # Retrieve full endpoint with a cluster name (outbound|9411||zipkin.istio-system.svc.cluster.local).
  istioctl proxy-config endpoint &lt;pod-name[.namespace]&gt; --cluster &#34;outbound|9411||zipkin.istio-system.svc.cluster.local&#34; -o json
  # Retrieve full endpoint with the status (healthy).
  istioctl proxy-config endpoint &lt;pod-name[.namespace]&gt; --status healthy -ojson

  # Retrieve endpoint summary without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/clusters?format=json&#39; &gt; envoy-clusters.json
  istioctl proxy-config endpoints --file envoy-clusters.json

</code></pre>
<h2 id="istioctl-proxy-config-listener">istioctl proxy-config listener</h2>
<p>Retrieve information about listener configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config listener [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config listeners [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
istioctl proxy-config l [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--address &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by address field  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--port &lt;int&gt;</code></td>
<td></td>
<td>Filter listeners by Port field  (default `0`)</td>
</tr>
<tr>
<td><code>--type &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by type field  (default ``)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td></td>
<td>Output more information </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-listener Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve summary about listener configuration for a given pod from Envoy.
  istioctl proxy-config listeners &lt;pod-name[.namespace]&gt;

  # Retrieve listener summary for listeners with port 9080.
  istioctl proxy-config listeners &lt;pod-name[.namespace]&gt; --port 9080

  # Retrieve full listener dump for HTTP listeners with a wildcard address (0.0.0.0).
  istioctl proxy-config listeners &lt;pod-name[.namespace]&gt; --type HTTP --address 0.0.0.0 -o json

  # Retrieve listener summary without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config listeners --file envoy-config.json

</code></pre>
<h2 id="istioctl-proxy-config-log">istioctl proxy-config log</h2>
<p>(experimental) Retrieve information about logging levels of the Envoy instance in the specified pod, and update optionally</p>
<pre class="language-bash"><code>istioctl proxy-config log [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config o [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--level &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated minimum per-logger level of messages to output, in the form of [&lt;logger&gt;:]&lt;level&gt;,[&lt;logger&gt;:]&lt;level&gt;,... where logger can be one of admin, aws, assert, backtrace, client, config, connection, conn_handler, dubbo, file, filter, forward_proxy, grpc, hc, health_checker, http, http2, hystrix, init, io, jwt, kafka, lua, main, misc, mongo, quic, pool, rbac, redis, router, runtime, stats, secret, tap, testing, thrift, tracing, upstream, udp, wasm and level can be one of [trace, debug, info, warning, error, critical, off]  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--reset</code></td>
<td><code>-r</code></td>
<td>Reset levels to default value (warning). </td>
</tr>
<tr>
<td><code>--selector &lt;string&gt;</code></td>
<td><code>-l</code></td>
<td>Label selector  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-log Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve information about logging levels for a given pod from Envoy.
  istioctl proxy-config log &lt;pod-name[.namespace]&gt;

  # Update levels of the all loggers
  istioctl proxy-config log &lt;pod-name[.namespace]&gt; --level none

  # Update levels of the specified loggers.
  istioctl proxy-config log &lt;pod-name[.namespace]&gt; --level http:debug,redis:debug

  # Reset levels of all the loggers to default value (warning).
  istioctl proxy-config log &lt;pod-name[.namespace]&gt; -r

</code></pre>
<h2 id="istioctl-proxy-config-rootca-compare">istioctl proxy-config rootca-compare</h2>
<p>Compare ROOTCA values for given 2 pods to check the connectivity between them.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl proxy-config rootca-compare [pod/]&lt;name-1&gt;[.&lt;namespace-1&gt;] [pod/]&lt;name-2&gt;[.&lt;namespace-2&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config rc [pod/]&lt;name-1&gt;[.&lt;namespace-1&gt;] [pod/]&lt;name-2&gt;[.&lt;namespace-2&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-rootca-compare Examples">Examples</h3>
<pre class="language-bash"><code>  # Compare ROOTCA values for given 2 pods to check the connectivity between them.
  istioctl proxy-config rootca-compare &lt;pod-name-1[.namespace]&gt; &lt;pod-name-2[.namespace]&gt;
</code></pre>
<h2 id="istioctl-proxy-config-route">istioctl proxy-config route</h2>
<p>Retrieve information about route configuration for the Envoy instance in the specified pod.</p>
<pre class="language-bash"><code>istioctl proxy-config route [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config routes [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
istioctl proxy-config r [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--name &lt;string&gt;</code></td>
<td></td>
<td>Filter listeners by route name field  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--verbose</code></td>
<td></td>
<td>Output more information </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-route Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve summary about route configuration for a given pod from Envoy.
  istioctl proxy-config routes &lt;pod-name[.namespace]&gt;

  # Retrieve route summary for route 9080.
  istioctl proxy-config route &lt;pod-name[.namespace]&gt; --name 9080

  # Retrieve full route dump for route 9080
  istioctl proxy-config route &lt;pod-name[.namespace]&gt; --name 9080 -o json

  # Retrieve route summary without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config routes --file envoy-config.json

</code></pre>
<h2 id="istioctl-proxy-config-secret">istioctl proxy-config secret</h2>
<p>Retrieve information about secret configuration for the Envoy instance in the specified pod.</p>
<p>THIS COMMAND IS UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.</p>
<pre class="language-bash"><code>istioctl proxy-config secret [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl proxy-config secrets [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
istioctl proxy-config s [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>Output format: one of json|yaml|short  (default `short`)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-config-secret Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve full secret configuration for a given pod from Envoy.
  istioctl proxy-config secret &lt;pod-name[.namespace]&gt;

  # Retrieve full bootstrap without using Kubernetes API
  ssh &lt;user@hostname&gt; &#39;curl localhost:15000/config_dump&#39; &gt; envoy-config.json
  istioctl proxy-config secret --file envoy-config.json
</code></pre>
<h2 id="istioctl-proxy-status">istioctl proxy-status</h2>
<p>
Retrieves last sent and last acknowledged xDS sync from Istiod to each Envoy in the mesh</p>
<p></p>
<pre class="language-bash"><code>istioctl proxy-status [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl ps [&lt;type&gt;/]&lt;name&gt;[.&lt;namespace&gt;] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--file &lt;string&gt;</code></td>
<td><code>-f</code></td>
<td>Envoy config dump JSON file  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-proxy-status Examples">Examples</h3>
<pre class="language-bash"><code>  # Retrieve sync status for all Envoys in a mesh
  istioctl proxy-status

  # Retrieve sync diff for a single Envoy and Istiod
  istioctl proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system

  # Retrieve sync diff between Istiod and one pod under a deployment
  istioctl proxy-status deployment/productpage-v1

  # Write proxy config-dump to file, and compare to Istio control plane
  kubectl port-forward -n istio-system istio-egressgateway-59585c5b9c-ndc59 15000 &amp;
  curl localhost:15000/config_dump &gt; cd.json
  istioctl proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system --file cd.json

</code></pre>
<h2 id="istioctl-tag">istioctl tag</h2>
<p>Command group used to interact with revision tags. Revision tags allow for the creation of mutable aliases
referring to control plane revisions for sidecar injection.</p>
<p>With revision tags, rather than relabeling a namespace from &#34;istio.io/rev=revision-a&#34; to &#34;istio.io/rev=revision-b&#34; to
change which control plane revision handles injection, it&#39;s possible to create a revision tag &#34;prod&#34; and label our
namespace &#34;istio.io/rev=prod&#34;. The &#34;prod&#34; revision tag could point to &#34;1-7-6&#34; initially and then be changed to point to &#34;1-8-1&#34;
at some later point.</p>
<p>This allows operators to change which Istio control plane revision should handle injection for a namespace or set of namespaces
without manual relabeling of the &#34;istio.io/rev&#34; tag.
</p>
<pre class="language-bash"><code>istioctl tag [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-tag-generate">istioctl tag generate</h2>
<p>Create a revision tag and output to the command&#39;s stdout. Tag an Istio control plane revision for use with namespace istio.io/rev
injection labels.</p>
<pre class="language-bash"><code>istioctl tag generate &lt;revision-tag&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--auto-inject-namespaces</code></td>
<td></td>
<td>If set to true, the sidecars should be automatically injected into all namespaces by default </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--overwrite</code></td>
<td></td>
<td>If true, allow revision tags to be overwritten, otherwise reject revision tag updates that
overwrite existing revision tags. </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision to reference from a given revision tag  (default ``)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--webhook-name &lt;string&gt;</code></td>
<td></td>
<td>Name to use for a revision tag&#39;s mutating webhook configuration.  (default ``)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-tag-generate Examples">Examples</h3>
<pre class="language-bash"><code> # Create a revision tag from the &#34;1-8-0&#34; revision
 istioctl tag generate prod --revision 1-8-0 &gt; tag.yaml

 # Apply the tag to cluster
 kubectl apply -f tag.yaml

 # Point namespace &#34;test-ns&#34; at the revision pointed to by the &#34;prod&#34; revision tag
 kubectl label ns test-ns istio.io/rev=prod

 # Rollout namespace &#34;test-ns&#34; to update workloads to the &#34;1-8-0&#34; revision
 kubectl rollout restart deployments -n test-ns

</code></pre>
<h2 id="istioctl-tag-list">istioctl tag list</h2>
<p>List existing revision tags</p>
<pre class="language-bash"><code>istioctl tag list [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl tag show [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-tag-list Examples">Examples</h3>
<pre class="language-bash"><code>istioctl tag list
</code></pre>
<h2 id="istioctl-tag-remove">istioctl tag remove</h2>
<p>Remove Istio control plane revision tag.</p>
<p>Removing a revision tag should be done with care. Removing a revision tag will disrupt sidecar injection in namespaces
that reference the tag in an &#34;istio.io/rev&#34; label. Verify that there are no remaining namespaces referencing a
revision tag before removing using the &#34;istioctl tag list&#34; command.
</p>
<pre class="language-bash"><code>istioctl tag remove &lt;revision-tag&gt; [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl tag delete &lt;revision-tag&gt; [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-tag-remove Examples">Examples</h3>
<pre class="language-bash"><code> # Remove the revision tag &#34;prod&#34;
	istioctl tag remove prod

</code></pre>
<h2 id="istioctl-tag-set">istioctl tag set</h2>
<p>Create or modify revision tags. Tag an Istio control plane revision for use with namespace istio.io/rev
injection labels.</p>
<pre class="language-bash"><code>istioctl tag set &lt;revision-tag&gt; [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--auto-inject-namespaces</code></td>
<td></td>
<td>If set to true, the sidecars should be automatically injected into all namespaces by default </td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--overwrite</code></td>
<td></td>
<td>If true, allow revision tags to be overwritten, otherwise reject revision tag updates that
overwrite existing revision tags. </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision to reference from a given revision tag  (default ``)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
<tr>
<td><code>--webhook-name &lt;string&gt;</code></td>
<td></td>
<td>Name to use for a revision tag&#39;s mutating webhook configuration.  (default ``)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-tag-set Examples">Examples</h3>
<pre class="language-bash"><code> # Create a revision tag from the &#34;1-8-0&#34; revision
 istioctl tag set prod --revision 1-8-0

 # Point namespace &#34;test-ns&#34; at the revision pointed to by the &#34;prod&#34; revision tag
 kubectl label ns test-ns istio.io/rev=prod

 # Change the revision tag to reference the &#34;1-8-1&#34; revision
 istioctl tag set prod --revision 1-8-1 --overwrite

 # Make revision &#34;1-8-1&#34; the default revision, both resulting in that revision handling injection for &#34;istio-injection=enabled&#34;
 # and validating resources cluster-wide
 istioctl tag set default --revision 1-8-1

 # Rollout namespace &#34;test-ns&#34; to update workloads to the &#34;1-8-1&#34; revision
 kubectl rollout restart deployments -n test-ns

</code></pre>
<h2 id="istioctl-upgrade">istioctl upgrade</h2>
<p>The upgrade command is an alias for the install command that performs additional upgrade-related checks.</p>
<pre class="language-bash"><code>istioctl upgrade [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--charts &lt;string&gt;</code></td>
<td></td>
<td>Deprecated, use --manifests instead.  (default ``)</td>
</tr>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<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;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Path to file containing IstioOperator custom resource
This flag can be specified multiple times to overlay multiple files. Multiple files are overlaid in left to right order.  (default `[]`)</td>
</tr>
<tr>
<td><code>--force</code></td>
<td></td>
<td>Proceed even with validation errors. </td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--readiness-timeout &lt;duration&gt;</code></td>
<td></td>
<td>Maximum time to wait for Istio resources in each component to be ready.  (default `5m0s`)</td>
</tr>
<tr>
<td><code>--set &lt;stringArray&gt;</code></td>
<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.15/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec  (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-confirmation</code></td>
<td><code>-y</code></td>
<td>The skipConfirmation determines whether the user is prompted for confirmation.
If set to true, the user is not prompted and a Yes response is assumed in all cases. </td>
</tr>
<tr>
<td><code>--verify</code></td>
<td></td>
<td>Verify the Istio control plane after installation/in-place upgrade </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="istioctl-validate">istioctl validate</h2>
<p>Validate Istio policy and rules files</p>
<pre class="language-bash"><code>istioctl validate -f FILENAME [options] [flags]
</code></pre>
<div class="aliases">
<pre class="language-bash"><code>istioctl v -f FILENAME [options] [flags]
</code></pre></div>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--filename &lt;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Names of files to validate  (default `[]`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--referential</code></td>
<td><code>-x</code></td>
<td>Enable structural validation for policy and telemetry </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-validate Examples">Examples</h3>
<pre class="language-bash"><code>  # Validate bookinfo-gateway.yaml
  istioctl validate -f samples/bookinfo/networking/bookinfo-gateway.yaml

  # Validate bookinfo-gateway.yaml with shorthand syntax
  istioctl v -f samples/bookinfo/networking/bookinfo-gateway.yaml

  # Validate current deployments under &#39;default&#39; namespace within the cluster
  kubectl get deployments -o yaml | istioctl validate -f -

  # Validate current services under &#39;default&#39; namespace within the cluster
  kubectl get services -o yaml | istioctl validate -f -

  # Also see the related command &#39;istioctl analyze&#39;
  istioctl analyze samples/bookinfo/networking/bookinfo-gateway.yaml

</code></pre>
<h2 id="istioctl-verify-install">istioctl verify-install</h2>
<p>
verify-install verifies Istio installation status against the installation file
you specified when you installed Istio. It loops through all the installation
resources defined in your installation file and reports whether all of them are
in ready status. It will report failure when any of them are not ready.</p>
<p>If you do not specify an installation it will check for an IstioOperator resource
and will verify if pods and services defined in it are present.</p>
<p>Note: For verifying whether your cluster is ready for Istio installation, see
istioctl experimental precheck.
</p>
<pre class="language-bash"><code>istioctl verify-install [-f &lt;deployment or istio operator file&gt;] [--revision &lt;revision&gt;] [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--filename &lt;stringSlice&gt;</code></td>
<td><code>-f</code></td>
<td>Istio YAML installation file.  (default `[]`)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<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.15.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.15.0/istio-1.15.0-linux-amd64.tar.gz).
  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h3 id="istioctl-verify-install Examples">Examples</h3>
<pre class="language-bash"><code>  # Verify that Istio is installed correctly via Istio Operator
  istioctl verify-install

  # Verify the deployment matches a custom Istio deployment configuration
  istioctl verify-install -f $HOME/istio.yaml

  # Verify the deployment matches the Istio Operator deployment definition
  istioctl verify-install --revision &lt;canary&gt;

  # Verify the installation of specific revision
  istioctl verify-install -r 1-9-0
</code></pre>
<h2 id="istioctl-version">istioctl version</h2>
<p>Prints out build version information</p>
<pre class="language-bash"><code>istioctl version [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Shorthand</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--context &lt;string&gt;</code></td>
<td></td>
<td>The name of the kubeconfig context to use  (default ``)</td>
</tr>
<tr>
<td><code>--istioNamespace &lt;string&gt;</code></td>
<td><code>-i</code></td>
<td>Istio system namespace  (default `istio-system`)</td>
</tr>
<tr>
<td><code>--kubeconfig &lt;string&gt;</code></td>
<td><code>-c</code></td>
<td>Kubernetes configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--namespace &lt;string&gt;</code></td>
<td><code>-n</code></td>
<td>Config namespace  (default ``)</td>
</tr>
<tr>
<td><code>--output &lt;string&gt;</code></td>
<td><code>-o</code></td>
<td>One of &#39;yaml&#39; or &#39;json&#39;.  (default ``)</td>
</tr>
<tr>
<td><code>--remote</code></td>
<td></td>
<td>Use --remote=false to suppress control plane check </td>
</tr>
<tr>
<td><code>--revision &lt;string&gt;</code></td>
<td><code>-r</code></td>
<td>Control plane revision  (default ``)</td>
</tr>
<tr>
<td><code>--short</code></td>
<td><code>-s</code></td>
<td>Use --short=false to generate full version information </td>
</tr>
<tr>
<td><code>--vklog &lt;Level&gt;</code></td>
<td></td>
<td>number for the log level verbosity. Like -v flag. ex: --vklog=9  (default `0`)</td>
</tr>
</tbody>
</table>
<h2 id="envvars">Environment variables</h2>
These environment variables affect the behavior of the <code>istioctl</code> command. Please use with caution as these environment variables are experimental and can change anytime.
<table class="envvars">
<thead>
<tr>
<th>Variable Name</th>
<th>Type</th>
<th>Default Value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>AUTO_RELOAD_PLUGIN_CERTS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, if user introduces new intermediate plug-in CA, user need not to restart istiod to pick up certs.Istiod picks newly added intermediate plug-in CA certs and updates it. Plug-in new Root-CA not supported.</td>
</tr>
<tr>
<td><code>CERT_SIGNER_DOMAIN</code></td>
<td>String</td>
<td><code></code></td>
<td>The cert signer domain info</td>
</tr>
<tr>
<td><code>CLOUD_PLATFORM</code></td>
<td>String</td>
<td><code></code></td>
<td>Cloud Platform on which proxy is running, if not specified, Istio will try to discover the platform. Valid platform values are aws, azure, gcp, none</td>
</tr>
<tr>
<td><code>CLUSTER_ID</code></td>
<td>String</td>
<td><code>Kubernetes</code></td>
<td>Defines the cluster and service registry that this Istiod instance is belongs to</td>
</tr>
<tr>
<td><code>ENABLE_AUTO_MTLS_CHECK_POLICIES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Enable the auto mTLS EDS output to consult the PeerAuthentication Policy, only set the {tlsMode: istio}  when server side policy enables mTLS PERMISSIVE or STRICT.</td>
</tr>
<tr>
<td><code>ENABLE_AUTO_SNI</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, automatically set SNI when `DestinationRules` do not specify the same</td>
</tr>
<tr>
<td><code>ENABLE_CA_SERVER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If this is set to false, will not create CA server in istiod.</td>
</tr>
<tr>
<td><code>ENABLE_DEBUG_ON_HTTP</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If this is set to false, the debug interface will not be enabled, recommended for production</td>
</tr>
<tr>
<td><code>ENABLE_HCM_INTERNAL_NETWORKS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enable, endpoints defined in mesh networks will be configured as internal addresses in Http Connection Manager</td>
</tr>
<tr>
<td><code>ENABLE_LEGACY_FSGROUP_INJECTION</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<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_LEGACY_LB_ALGORITHM_DEFAULT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, destinations for which no LB algorithm is specified will use the legacy default, ROUND_ROBIN. Care should be taken when using ROUND_ROBIN in general as it can overburden endpoints, especially when weights are used.</td>
</tr>
<tr>
<td><code>ENABLE_MCS_AUTO_EXPORT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, istiod will automatically generate Kubernetes Multi-Cluster Services (MCS) ServiceExport resources for every service in the mesh. Services defined to be cluster-local in MeshConfig are excluded.</td>
</tr>
<tr>
<td><code>ENABLE_MCS_CLUSTER_LOCAL</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, istiod will treat the host `&lt;svc&gt;.&lt;namespace&gt;.svc.cluster.local` as defined by the Kubernetes Multi-Cluster Services (MCS) spec. In this mode, requests to `cluster.local` will be routed to only those endpoints residing within the same cluster as the client. Requires that both ENABLE_MCS_SERVICE_DISCOVERY and ENABLE_MCS_HOST also be enabled.</td>
</tr>
<tr>
<td><code>ENABLE_MCS_HOST</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, istiod will configure a Kubernetes Multi-Cluster Services (MCS) host (&lt;svc&gt;.&lt;namespace&gt;.svc.clusterset.local) for each service exported (via ServiceExport) in at least one cluster. Clients must, however, be able to successfully lookup these DNS hosts. That means that either Istio DNS interception must be enabled or an MCS controller must be used. Requires that ENABLE_MCS_SERVICE_DISCOVERY also be enabled.</td>
</tr>
<tr>
<td><code>ENABLE_MCS_SERVICE_DISCOVERY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, istiod will enable Kubernetes Multi-Cluster Services (MCS) service discovery mode. In this mode, service endpoints in a cluster will only be discoverable within the same cluster unless explicitly exported via ServiceExport.</td>
</tr>
<tr>
<td><code>ENABLE_MULTICLUSTER_HEADLESS</code></td>
<td>Boolean</td>
<td><code>true</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_PROBE_KEEPALIVE_CONNECTIONS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, readiness probes will keep the connection from pilot-agent to the application alive. This mirrors older Istio versions&#39; behaviors, but not kubelet&#39;s.</td>
</tr>
<tr>
<td><code>ENABLE_TLS_ON_SIDECAR_INGRESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, the TLS configuration on Sidecar.ingress will take effect</td>
</tr>
<tr>
<td><code>ENABLE_WASM_TELEMETRY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, Wasm-based telemetry will be enabled.</td>
</tr>
<tr>
<td><code>EXTERNAL_ISTIOD</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If this is set to true, one Istiod will control remote clusters including CA.</td>
</tr>
<tr>
<td><code>GCP_METADATA</code></td>
<td>String</td>
<td><code></code></td>
<td>Pipe separated GCP metadata, schemed as PROJECT_ID|PROJECT_NUMBER|CLUSTER_NAME|CLUSTER_ZONE</td>
</tr>
<tr>
<td><code>GCP_QUOTA_PROJECT</code></td>
<td>String</td>
<td><code></code></td>
<td>Allows specification of a quota project to be used in requests to GCP APIs.</td>
</tr>
<tr>
<td><code>HTTP_STRIP_FRAGMENT_FROM_PATH_UNSAFE_IF_DISABLED</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td></td>
</tr>
<tr>
<td><code>INJECTION_WEBHOOK_CONFIG_NAME</code></td>
<td>String</td>
<td><code>istio-sidecar-injector</code></td>
<td>Name of the mutatingwebhookconfiguration to patch, if istioctl is not used.</td>
</tr>
<tr>
<td><code>ISTIOCONFIG</code></td>
<td>String</td>
<td><code>$HOME/.istioctl/config.yaml</code></td>
<td>Default values for istioctl flags</td>
</tr>
<tr>
<td><code>ISTIOCTL_AUTHORITY</code></td>
<td>String</td>
<td><code></code></td>
<td>The istioctl --authority override</td>
</tr>
<tr>
<td><code>ISTIOCTL_CERT_DIR</code></td>
<td>String</td>
<td><code></code></td>
<td>The istioctl --cert-dir override</td>
</tr>
<tr>
<td><code>ISTIOCTL_INSECURE</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>The istioctl --insecure override</td>
</tr>
<tr>
<td><code>ISTIOCTL_ISTIONAMESPACE</code></td>
<td>String</td>
<td><code>istio-system</code></td>
<td>The istioctl --istioNamespace override</td>
</tr>
<tr>
<td><code>ISTIOCTL_PLAINTEXT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>The istioctl --plaintext override</td>
</tr>
<tr>
<td><code>ISTIOCTL_PREFER_EXPERIMENTAL</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>The istioctl should use experimental subcommand variants</td>
</tr>
<tr>
<td><code>ISTIOCTL_XDS_ADDRESS</code></td>
<td>String</td>
<td><code></code></td>
<td>The istioctl --xds-address override</td>
</tr>
<tr>
<td><code>ISTIOCTL_XDS_PORT</code></td>
<td>Integer</td>
<td><code>15012</code></td>
<td>The istioctl --xds-port override</td>
</tr>
<tr>
<td><code>ISTIOD_CUSTOM_HOST</code></td>
<td>String</td>
<td><code></code></td>
<td>Custom host name of istiod that istiod signs the server cert. Multiple custom host names are supported, and multiple values are separated by commas.</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>
<td>Default Http and gRPC Request timeout</td>
</tr>
<tr>
<td><code>ISTIO_DELTA_XDS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, pilot will only send the delta configs as opposed to the state of the world on a Resource Request. This feature uses the delta xds api, but does not currently send the actual deltas.</td>
</tr>
<tr>
<td><code>ISTIO_GATEWAY_STRIP_HOST_PORT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, Gateway will remove any port from host/authority header before any processing of request by HTTP filters or routing.</td>
</tr>
<tr>
<td><code>ISTIO_GPRC_MAXRECVMSGSIZE</code></td>
<td>Integer</td>
<td><code>4194304</code></td>
<td>Sets the max receive buffer size of gRPC stream in bytes.</td>
</tr>
<tr>
<td><code>ISTIO_GPRC_MAXSTREAMS</code></td>
<td>Integer</td>
<td><code>100000</code></td>
<td>Sets the maximum number of concurrent grpc streams.</td>
</tr>
<tr>
<td><code>ISTIO_MULTIROOT_MESH</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, mesh will support certificates signed by more than one trustAnchor for ISTIO_MUTUAL mTLS</td>
</tr>
<tr>
<td><code>ISTIO_PROMETHEUS_ANNOTATIONS</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>JWT_POLICY</code></td>
<td>String</td>
<td><code>third-party-jwt</code></td>
<td>The JWT validation policy.</td>
</tr>
<tr>
<td><code>K8S_INGRESS_NS</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>K_REVISION</code></td>
<td>String</td>
<td><code></code></td>
<td>KNative revision, set if running in knative</td>
</tr>
<tr>
<td><code>LABEL_CANONICAL_SERVICES_FOR_MESH_EXTERNAL_SERVICE_ENTRIES</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, metadata representing canonical services for ServiceEntry resources with a location of mesh_external will be populatedin the cluster metadata for those endpoints.</td>
</tr>
<tr>
<td><code>LOCAL_CLUSTER_SECRET_WATCHER</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, the cluster secret watcher will watch the namespace of the external cluster instead of config cluster</td>
</tr>
<tr>
<td><code>MCS_API_GROUP</code></td>
<td>String</td>
<td><code>multicluster.x-k8s.io</code></td>
<td>The group to be used for the Kubernetes Multi-Cluster Services (MCS) API.</td>
</tr>
<tr>
<td><code>MCS_API_VERSION</code></td>
<td>String</td>
<td><code>v1alpha1</code></td>
<td>The version to be used for the Kubernets Multi-Cluster Services (MCS) API.</td>
</tr>
<tr>
<td><code>PILOT_ANALYSIS_INTERVAL</code></td>
<td>Time Duration</td>
<td><code>10s</code></td>
<td>If analysis is enabled, pilot will run istio analyzers using this value as interval in seconds Istio Resources</td>
</tr>
<tr>
<td><code>PILOT_CERT_PROVIDER</code></td>
<td>String</td>
<td><code>istiod</code></td>
<td>The provider of Pilot DNS certificate.</td>
</tr>
<tr>
<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 interval. If no change is detected within this period, the push will happen,  otherwise we&#39;ll keep delaying until things settle, up to a max of PILOT_DEBOUNCE_MAX.</td>
</tr>
<tr>
<td><code>PILOT_DEBOUNCE_MAX</code></td>
<td>Time Duration</td>
<td><code>10s</code></td>
<td>The maximum amount of time to wait for events while debouncing. If events keep showing up with no breaks for this time, we&#39;ll trigger a push.</td>
</tr>
<tr>
<td><code>PILOT_DISTRIBUTION_HISTORY_RETENTION</code></td>
<td>Time Duration</td>
<td><code>1m0s</code></td>
<td>If enabled, Pilot will keep track of old versions of distributed config for this duration.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_ALPN_FILTER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, pilot will add Istio ALPN filters, required for proper protocol sniffing.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_ANALYSIS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, pilot will run istio analyzers and write analysis errors to the Status field of any Istio Resources</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_CDS_CACHE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, Pilot will cache CDS responses. Note: this depends on PILOT_ENABLE_XDS_CACHE.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_CONFIG_DISTRIBUTION_TRACKING</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Pilot will assign meaningful nonces to each Envoy configuration message, and allow users to interrogate which envoy has which config from the debug interface.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_CROSS_CLUSTER_WORKLOAD_ENTRY</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, pilot will read WorkloadEntry from other clusters, selectable by Services in that cluster.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_DESTINATION_RULE_INHERITANCE</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If set, workload specific DestinationRules will inherit configurations settings from mesh and namespace level rules</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_EDS_DEBOUNCE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Pilot will include EDS pushes in the push debouncing, configured by PILOT_DEBOUNCE_AFTER and PILOT_DEBOUNCE_MAX. EDS pushes may be delayed, but there will be fewer pushes. By default this is enabled</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_EDS_FOR_HEADLESS_SERVICES</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, for headless service in Kubernetes, pilot will send endpoints over EDS, allowing the sidecar to load balance among pods in the headless service. This feature should be enabled if applications access all services explicitly via a HTTP proxy port in the sidecar.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_GATEWAY_API</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If this is set to true, support for Kubernetes gateway-api (github.com/kubernetes-sigs/gateway-api) will  be enabled. In addition to this being enabled, the gateway-api CRDs need to be installed.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_GATEWAY_API_DEPLOYMENT_CONTROLLER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If this is set to true, gateway-api resources will automatically provision in cluster deployment, services, etc</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>
<td>If enabled, for a headless service/stateful set in Kubernetes, pilot will generate an outbound listener for each pod in a headless service. This feature should be disabled if headless services have a large number of pods.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_INBOUND_PASSTHROUGH</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, inbound clusters will be configured as ORIGINAL_DST clusters. When disabled, requests are always sent to localhost. The primary implication of this is that when enabled, binding to POD_IP will work while localhost will not; when disable, bind to POD_IP will not work, while localhost will. The enabled behavior matches the behavior without Istio enabled at all; this flag exists only for backwards compatibility. Regardless of this setting, the configuration can be overridden with the Sidecar.Ingress.DefaultEndpoint configuration.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_ISTIO_TAGS</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Determines whether or not trace spans generated by Envoy will include Istio-specific tags.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_LEGACY_AUTO_PASSTHROUGH</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, pilot will allow any upstream cluster to be used with AUTO_PASSTHROUGH. This option is intended for backwards compatibility only and is not secure with untrusted downstreams; it will be removed in the future.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_LEGACY_ISTIO_MUTUAL_CREDENTIAL_NAME</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, Gateway&#39;s with ISTIO_MUTUAL mode and credentialName configured will use simple TLS. This is to retain legacy behavior only and not recommended for use beyond migration.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_METADATA_EXCHANGE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, pilot will add metadata exchange filters, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_MONGO_FILTER</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>EnableMongoFilter enables injection of `envoy.filters.network.mongo_proxy` in the filter chain.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_MYSQL_FILTER</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>EnableMysqlFilter enables injection of `envoy.filters.network.mysql_proxy` in the filter chain.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_INBOUND</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, protocol sniffing will be used for inbound listeners whose port protocol is not specified or unsupported</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_PROTOCOL_SNIFFING_FOR_OUTBOUND</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, protocol sniffing will be used for outbound listeners whose port protocol is not specified or unsupported</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_QUIC_LISTENERS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, QUIC listeners will be generated wherever there are listeners terminating TLS on gateways if the gateway service exposes a UDP port with the same number (for example 443/TCP and 443/UDP)</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_RDS_CACHE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, Pilot will cache RDS responses. Note: this depends on PILOT_ENABLE_XDS_CACHE.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_REDIS_FILTER</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>EnableRedisFilter enables injection of `envoy.filters.network.redis_proxy` in the filter chain.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_ROUTE_COLLAPSE_OPTIMIZATION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, Pilot will merge virtual hosts with the same routes into a single virtual host, as an optimization.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_SERVICEENTRY_SELECT_PODS</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, service entries with selectors will select pods from the cluster. It is safe to disable it if you are quite sure you don&#39;t need this feature</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_STATUS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, pilot will update the CRD Status field of all istio resources with reconciliation status.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_TELEMETRY_LABEL</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, pilot will add telemetry related metadata to cluster and endpoint resources, which will be consumed by telemetry filter.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_WORKLOAD_ENTRY_AUTOREGISTRATION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Enables auto-registering WorkloadEntries based on associated WorkloadGroups upon XDS connection by the workload.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_WORKLOAD_ENTRY_HEALTHCHECKS</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Enables automatic health checks of WorkloadEntries based on the config provided in the associated WorkloadGroup</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_XDS_CACHE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, Pilot will cache XDS responses.</td>
</tr>
<tr>
<td><code>PILOT_ENABLE_XDS_IDENTITY_CHECK</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, pilot will authorize XDS clients, to ensure they are acting only as namespaces they have permissions for.</td>
</tr>
<tr>
<td><code>PILOT_ENDPOINT_TELEMETRY_LABEL</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<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>
<td>If enabled, Pilot will send only clusters that referenced in gateway virtual services attached to gateway</td>
</tr>
<tr>
<td><code>PILOT_HTTP10</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Enables the use of HTTP 1.0 in the outbound HTTP listeners, to support legacy applications.</td>
</tr>
<tr>
<td><code>PILOT_INBOUND_PROTOCOL_DETECTION_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>1s</code></td>
<td>Protocol detection timeout for inbound listener</td>
</tr>
<tr>
<td><code>PILOT_INSECURE_MULTICLUSTER_KUBECONFIG_OPTIONS</code></td>
<td>String</td>
<td><code></code></td>
<td>Comma separated list of potentially insecure kubeconfig authentication options that are allowed for multicluster authentication.Support values: all authProviders (`gcp`, `azure`, `exec`, `openstack`), `clientKey`, `clientCertificate`, `tokenFile`, and `exec`.</td>
</tr>
<tr>
<td><code>PILOT_JWT_ENABLE_REMOTE_JWKS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, checks to see if the configured JwksUri in RequestAuthentication is a mesh cluster URL and configures remote Jwks to let Envoy fetch the Jwks instead of Istiod.</td>
</tr>
<tr>
<td><code>PILOT_JWT_PUB_KEY_REFRESH_INTERVAL</code></td>
<td>Time Duration</td>
<td><code>20m0s</code></td>
<td>The interval for istiod to fetch the jwks_uri for the jwks public key.</td>
</tr>
<tr>
<td><code>PILOT_LEGACY_INGRESS_BEHAVIOR</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If this is set to true, istio ingress will perform the legacy behavior, which does not meet https://kubernetes.io/docs/concepts/services-networking/ingress/#multiple-matches.</td>
</tr>
<tr>
<td><code>PILOT_MAX_REQUESTS_PER_SECOND</code></td>
<td>Floating-Point</td>
<td><code>25</code></td>
<td>Limits the number of incoming XDS requests per second. On larger machines this can be increased to handle more proxies concurrently.</td>
</tr>
<tr>
<td><code>PILOT_PARTIAL_FULL_PUSHES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, pilot will send partial pushes in for child resources (RDS, EDS, etc) when possible. This occurs for EDS in many cases regardless of this setting.</td>
</tr>
<tr>
<td><code>PILOT_PUSH_REPEATED_NONCES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, pilot will send responses to XDS requests that have an already requested nonce.</td>
</tr>
<tr>
<td><code>PILOT_PUSH_THROTTLE</code></td>
<td>Integer</td>
<td><code>100</code></td>
<td>Limits the number of concurrent pushes allowed. On larger machines this can be increased for faster pushes</td>
</tr>
<tr>
<td><code>PILOT_REMOTE_CLUSTER_TIMEOUT</code></td>
<td>Time Duration</td>
<td><code>30s</code></td>
<td>After this timeout expires, pilot can become ready without syncing data from clusters added via remote-secrets. Setting the timeout to 0 disables this behavior.</td>
</tr>
<tr>
<td><code>PILOT_SCOPE_GATEWAY_TO_NAMESPACE</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, a gateway workload can only select gateway resources in the same namespace. Gateways with same selectors in different namespaces will not be applicable.</td>
</tr>
<tr>
<td><code>PILOT_SEND_UNHEALTHY_ENDPOINTS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, Pilot will include unhealthy endpoints in EDS pushes and even if they are sent Envoy does not use them for load balancing.  To avoid, sending traffic to non ready endpoints, enabling this flag, disables panic threshold in Envoy i.e. Envoy does not load balance requests to unhealthy/non-ready hosts even if the percentage of healthy hosts fall below minimum health percentage(panic threshold).</td>
</tr>
<tr>
<td><code>PILOT_SIDECAR_USE_REMOTE_ADDRESS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>UseRemoteAddress sets useRemoteAddress to true for side car outbound listeners.</td>
</tr>
<tr>
<td><code>PILOT_SKIP_VALIDATE_TRUST_DOMAIN</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Skip validating the peer is from the same trust domain when mTLS is enabled in authentication policy</td>
</tr>
<tr>
<td><code>PILOT_STATUS_BURST</code></td>
<td>Integer</td>
<td><code>500</code></td>
<td>If status is enabled, controls the Burst rate with which status will be updated.  See https://godoc.org/k8s.io/client-go/rest#Config Burst</td>
</tr>
<tr>
<td><code>PILOT_STATUS_MAX_WORKERS</code></td>
<td>Integer</td>
<td><code>100</code></td>
<td>The maximum number of workers Pilot will use to keep configuration status up to date.  Smaller numbers will result in higher status latency, but larger numbers may impact CPU in high scale environments.</td>
</tr>
<tr>
<td><code>PILOT_STATUS_QPS</code></td>
<td>Floating-Point</td>
<td><code>100</code></td>
<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>
<td>Sets the mesh-wide trace sampling percentage. Should be 0.0 - 100.0. Precision to 0.01. Default is 1.0.</td>
</tr>
<tr>
<td><code>PILOT_USE_ENDPOINT_SLICE</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, Pilot will use EndpointSlices as the source of endpoints for Kubernetes services. By default, this is false, and Endpoints will be used. This requires the Kubernetes EndpointSlice controller to be enabled. Currently this is mutual exclusive - either Endpoints or EndpointSlices will be used</td>
</tr>
<tr>
<td><code>PILOT_WORKLOAD_ENTRY_GRACE_PERIOD</code></td>
<td>Time Duration</td>
<td><code>10s</code></td>
<td>The amount of time an auto-registered workload can remain disconnected from all Pilot instances before the associated WorkloadEntry is cleaned up.</td>
</tr>
<tr>
<td><code>PILOT_XDS_CACHE_SIZE</code></td>
<td>Integer</td>
<td><code>60000</code></td>
<td>The maximum number of cache entries for the XDS cache.</td>
</tr>
<tr>
<td><code>PILOT_XDS_CACHE_STATS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If true, Pilot will collect metrics for XDS cache efficiency.</td>
</tr>
<tr>
<td><code>PILOT_XDS_SEND_TIMEOUT</code></td>
<td>Time Duration</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>
<td><code>POD_NAME</code></td>
<td>String</td>
<td><code></code></td>
<td></td>
</tr>
<tr>
<td><code>PRIORITIZED_LEADER_ELECTION</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, the default revision will steal leader locks from non-default revisions</td>
</tr>
<tr>
<td><code>REQUIRE_3P_TOKEN</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Reject k8s default tokens, without audience. If false, default K8S token will be accepted</td>
</tr>
<tr>
<td><code>RESOLVE_HOSTNAME_GATEWAYS</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, hostnames in the LoadBalancer addresses of a Service will be resolved at the control plane for use in cross-network gateways.</td>
</tr>
<tr>
<td><code>REWRITE_PROBE_LEGACY_LOCALHOST_DESTINATION</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, readiness probes will be sent to &#39;localhost&#39;. Otherwise, they will be sent to the Pod&#39;s IP, matching Kubernetes&#39; behavior.</td>
</tr>
<tr>
<td><code>REWRITE_TCP_PROBES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If false, TCP probes will not be rewritten and therefor always succeed when a sidecar is used.</td>
</tr>
<tr>
<td><code>SHARED_MESH_CONFIG</code></td>
<td>String</td>
<td><code></code></td>
<td>Additional config map to load for shared MeshConfig settings. The standard mesh config will take precedence.</td>
</tr>
<tr>
<td><code>SPIFFE_BUNDLE_ENDPOINTS</code></td>
<td>String</td>
<td><code></code></td>
<td>The SPIFFE bundle trust domain to endpoint mappings. Istiod retrieves the root certificate from each SPIFFE bundle endpoint and uses it to verify client certifiates from that trust domain. The endpoint must be compliant to the SPIFFE Bundle Endpoint standard. For details, please refer to https://github.com/spiffe/spiffe/blob/master/standards/SPIFFE_Trust_Domain_and_Bundle.md . No need to configure this for root certificates issued via Istiod or web-PKI based root certificates. Use || between &lt;trustdomain, endpoint&gt; tuples. Use | as delimiter between trust domain and endpoint in each tuple. For example: foo|https://url/for/foo||bar|https://url/for/bar</td>
</tr>
<tr>
<td><code>TERM</code></td>
<td>String</td>
<td><code></code></td>
<td>Specifies terminal type.  Use &#39;dumb&#39; to suppress color output</td>
</tr>
<tr>
<td><code>TOKEN_AUDIENCES</code></td>
<td>String</td>
<td><code>istio-ca</code></td>
<td>A list of comma separated audiences to check in the JWT token before issuing a certificate. The token is accepted if it matches with one of the audiences</td>
</tr>
<tr>
<td><code>TRUSTED_GATEWAY_CIDR</code></td>
<td>String</td>
<td><code></code></td>
<td>If set, any connections from gateway to Istiod with this CIDR range are treated as trusted for using authenication mechanisms like XFCC. This can only be used when the network where Istiod and the authenticating gateways are running in a trusted/secure network</td>
</tr>
<tr>
<td><code>UNSAFE_ENABLE_ADMIN_ENDPOINTS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If this is set to true, dangerous admin endpoints will be exposed on the debug interface. Not recommended for production.</td>
</tr>
<tr>
<td><code>UNSAFE_PILOT_ENABLE_DELTA_TEST</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, addition runtime tests for Delta XDS efficiency are added. These checks are extremely expensive, so this should be used only for testing, not production.</td>
</tr>
<tr>
<td><code>UNSAFE_PILOT_ENABLE_RUNTIME_ASSERTIONS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, addition runtime asserts will be performed. These checks are both expensive and panic on failure. As a result, this should be used only for testing.</td>
</tr>
<tr>
<td><code>VALIDATION_WEBHOOK_CONFIG_NAME</code></td>
<td>String</td>
<td><code>istio-istio-system</code></td>
<td>Name of the validatingwebhookconfiguration to patch. Empty will skip using cluster admin to patch.</td>
</tr>
<tr>
<td><code>VERIFY_CERTIFICATE_AT_CLIENT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>If enabled, certificates received by the proxy will be verified against the OS CA certificate bundle.</td>
</tr>
<tr>
<td><code>VERIFY_SDS_CERTIFICATE</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, certificates fetched from SDS server will be verified before sending back to proxy.</td>
</tr>
<tr>
<td><code>XDS_AUTH</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If true, will authenticate XDS clients.</td>
</tr>
<tr>
<td><code>XDS_AUTH_PLAINTEXT</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Authenticate plain text requests - used if Istiod is running on a secure/trusted network</td>
</tr>
</tbody>
</table>
<h2 id="metrics">Exported metrics</h2>
<table class="metrics">
<thead>
<tr><th>Metric Name</th><th>Type</th><th>Description</th></tr>
</thead>
<tbody>
<tr><td><code>auto_registration_deletes_total</code></td><td><code>Sum</code></td><td>Total number of auto registration cleaned up by periodic timer.</td></tr>
<tr><td><code>auto_registration_errors_total</code></td><td><code>Sum</code></td><td>Total number of auto registration errors.</td></tr>
<tr><td><code>auto_registration_success_total</code></td><td><code>Sum</code></td><td>Total number of successful auto registrations.</td></tr>
<tr><td><code>auto_registration_unregister_total</code></td><td><code>Sum</code></td><td>Total number of unregistrations.</td></tr>
<tr><td><code>auto_registration_updates_total</code></td><td><code>Sum</code></td><td>Total number of auto registration updates.</td></tr>
<tr><td><code>cache_flush_total</code></td><td><code>Sum</code></td><td>number of times operator cache was flushed</td></tr>
<tr><td><code>controller_sync_errors_total</code></td><td><code>Sum</code></td><td>Total number of errorMetric syncing controllers.</td></tr>
<tr><td><code>cr_deletion_total</code></td><td><code>Sum</code></td><td>Number of IstioOperator CR deleted</td></tr>
<tr><td><code>cr_merge_failure_total</code></td><td><code>Sum</code></td><td>Number of IstioOperator CR merge failures</td></tr>
<tr><td><code>cr_validation_error_total</code></td><td><code>Sum</code></td><td>Number of IstioOperator CR validation failures</td></tr>
<tr><td><code>endpoint_no_pod</code></td><td><code>LastValue</code></td><td>Endpoints without an associated pod.</td></tr>
<tr><td><code>get_cr_error_total</code></td><td><code>Sum</code></td><td>Number of times fetching CR from apiserver failed</td></tr>
<tr><td><code>istio_build</code></td><td><code>LastValue</code></td><td>Istio component build info</td></tr>
<tr><td><code>istiod_managed_clusters</code></td><td><code>LastValue</code></td><td>Number of clusters managed by istiod</td></tr>
<tr><td><code>legacy_path_translation_total</code></td><td><code>Sum</code></td><td>Number of times a legacy API path is translated</td></tr>
<tr><td><code>manifest_patch_error_total</code></td><td><code>Sum</code></td><td>Number of times K8S patch overlays failed</td></tr>
<tr><td><code>manifest_render_error_total</code></td><td><code>Sum</code></td><td>Number of times error occurred during rendering output manifest</td></tr>
<tr><td><code>num_outgoing_retries</code></td><td><code>Sum</code></td><td>Number of outgoing retry requests (e.g. to a token exchange server, CA, etc.)</td></tr>
<tr><td><code>owned_resource_total</code></td><td><code>LastValue</code></td><td>Number of resources currently owned by the operator</td></tr>
<tr><td><code>pilot_conflict_inbound_listener</code></td><td><code>LastValue</code></td><td>Number of conflicting inbound listeners.</td></tr>
<tr><td><code>pilot_conflict_outbound_listener_http_over_current_tcp</code></td><td><code>LastValue</code></td><td>Number of conflicting wildcard http listeners with current wildcard tcp listener.</td></tr>
<tr><td><code>pilot_conflict_outbound_listener_tcp_over_current_http</code></td><td><code>LastValue</code></td><td>Number of conflicting wildcard tcp listeners with current wildcard http listener.</td></tr>
<tr><td><code>pilot_conflict_outbound_listener_tcp_over_current_tcp</code></td><td><code>LastValue</code></td><td>Number of conflicting tcp listeners with current tcp listener.</td></tr>
<tr><td><code>pilot_destrule_subsets</code></td><td><code>LastValue</code></td><td>Duplicate subsets across destination rules for same host</td></tr>
<tr><td><code>pilot_duplicate_envoy_clusters</code></td><td><code>LastValue</code></td><td>Duplicate envoy clusters caused by service entries with same hostname</td></tr>
<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_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>
<tr><td><code>pilot_k8s_endpoints_pending_pod</code></td><td><code>LastValue</code></td><td>Number of endpoints that do not currently have any corresponding pods.</td></tr>
<tr><td><code>pilot_k8s_endpoints_with_no_pods</code></td><td><code>Sum</code></td><td>Endpoints that does not have any corresponding pods.</td></tr>
<tr><td><code>pilot_k8s_reg_events</code></td><td><code>Sum</code></td><td>Events from k8s registry.</td></tr>
<tr><td><code>pilot_no_ip</code></td><td><code>LastValue</code></td><td>Pods not found in the endpoint table, possibly invalid.</td></tr>
<tr><td><code>pilot_proxy_convergence_time</code></td><td><code>Distribution</code></td><td>Delay in seconds between config change and a proxy receiving all required configuration.</td></tr>
<tr><td><code>pilot_proxy_queue_time</code></td><td><code>Distribution</code></td><td>Time in seconds, a proxy is in the push queue before being dequeued.</td></tr>
<tr><td><code>pilot_push_triggers</code></td><td><code>Sum</code></td><td>Total number of times a push was triggered, labeled by reason for the push.</td></tr>
<tr><td><code>pilot_sds_certificate_errors_total</code></td><td><code>Sum</code></td><td>Total number of failures to fetch SDS key and certificate.</td></tr>
<tr><td><code>pilot_services</code></td><td><code>LastValue</code></td><td>Total services known to pilot.</td></tr>
<tr><td><code>pilot_total_rejected_configs</code></td><td><code>Sum</code></td><td>Total number of configs that Pilot had to reject or ignore.</td></tr>
<tr><td><code>pilot_total_xds_internal_errors</code></td><td><code>Sum</code></td><td>Total number of internal XDS errors in pilot.</td></tr>
<tr><td><code>pilot_total_xds_rejects</code></td><td><code>Sum</code></td><td>Total number of XDS responses from pilot rejected by proxy.</td></tr>
<tr><td><code>pilot_virt_services</code></td><td><code>LastValue</code></td><td>Total virtual services known to pilot.</td></tr>
<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>
<tr><td><code>pilot_xds_expired_nonce</code></td><td><code>Sum</code></td><td>Total number of XDS requests with an expired nonce.</td></tr>
<tr><td><code>pilot_xds_lds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected LDS.</td></tr>
<tr><td><code>pilot_xds_push_context_errors</code></td><td><code>Sum</code></td><td>Number of errors (timeouts) initiating push context.</td></tr>
<tr><td><code>pilot_xds_push_time</code></td><td><code>Distribution</code></td><td>Total time in seconds Pilot takes to push lds, rds, cds and eds.</td></tr>
<tr><td><code>pilot_xds_pushes</code></td><td><code>Sum</code></td><td>Pilot build and send errors for lds, rds, cds and eds.</td></tr>
<tr><td><code>pilot_xds_rds_reject</code></td><td><code>LastValue</code></td><td>Pilot rejected RDS.</td></tr>
<tr><td><code>pilot_xds_send_time</code></td><td><code>Distribution</code></td><td>Total time in seconds Pilot takes to send generated configuration.</td></tr>
<tr><td><code>pilot_xds_write_timeout</code></td><td><code>Sum</code></td><td>Pilot XDS response write timeouts.</td></tr>
<tr><td><code>remote_cluster_sync_timeouts_total</code></td><td><code>Sum</code></td><td>Number of times remote clusters took too long to sync, causing slow startup that excludes remote clusters.</td></tr>
<tr><td><code>render_manifest_total</code></td><td><code>Sum</code></td><td>Number of component manifests rendered</td></tr>
<tr><td><code>resource_creation_total</code></td><td><code>Sum</code></td><td>Number of resources created by the operator</td></tr>
<tr><td><code>resource_deletion_total</code></td><td><code>Sum</code></td><td>Number of resources deleted by the operator</td></tr>
<tr><td><code>resource_prune_total</code></td><td><code>Sum</code></td><td>Number of resources pruned by the operator</td></tr>
<tr><td><code>resource_update_total</code></td><td><code>Sum</code></td><td>Number of resources updated by the operator</td></tr>
<tr><td><code>scrape_failures_total</code></td><td><code>Sum</code></td><td>The total number of failed scrapes.</td></tr>
<tr><td><code>scrapes_total</code></td><td><code>Sum</code></td><td>The total number of scrapes.</td></tr>
<tr><td><code>sidecar_injection_failure_total</code></td><td><code>Sum</code></td><td>Total number of failed sidecar injection requests.</td></tr>
<tr><td><code>sidecar_injection_requests_total</code></td><td><code>Sum</code></td><td>Total number of sidecar injection requests.</td></tr>
<tr><td><code>sidecar_injection_skip_total</code></td><td><code>Sum</code></td><td>Total number of skipped sidecar injection requests.</td></tr>
<tr><td><code>sidecar_injection_success_total</code></td><td><code>Sum</code></td><td>Total number of successful sidecar injection requests.</td></tr>
<tr><td><code>startup_duration_seconds</code></td><td><code>LastValue</code></td><td>The time from the process starting to being marked ready.</td></tr>
<tr><td><code>version</code></td><td><code>LastValue</code></td><td>Version of operator binary</td></tr>
<tr><td><code>wasm_cache_entries</code></td><td><code>LastValue</code></td><td>number of Wasm remote fetch cache entries.</td></tr>
<tr><td><code>wasm_cache_lookup_count</code></td><td><code>Sum</code></td><td>number of Wasm remote fetch cache lookups.</td></tr>
<tr><td><code>wasm_config_conversion_count</code></td><td><code>Sum</code></td><td>number of Wasm config conversion count and results, including success, no remote load, marshal failure, remote fetch failure, miss remote fetch hint.</td></tr>
<tr><td><code>wasm_config_conversion_duration</code></td><td><code>Distribution</code></td><td>Total time in milliseconds istio-agent spends on converting remote load in Wasm config.</td></tr>
<tr><td><code>wasm_remote_fetch_count</code></td><td><code>Sum</code></td><td>number of Wasm remote fetches and results, including success, download failure, and checksum mismatch.</td></tr>
<tr><td><code>webhook_patch_attempts_total</code></td><td><code>Sum</code></td><td>Webhook patching attempts</td></tr>
<tr><td><code>webhook_patch_failures_total</code></td><td><code>Sum</code></td><td>Webhook patching total failures</td></tr>
<tr><td><code>webhook_patch_retries_total</code></td><td><code>Sum</code></td><td>Webhook patching retries</td></tr>
<tr><td><code>xds_cache_dependent_config_size</code></td><td><code>LastValue</code></td><td>Current size of dependent configs</td></tr>
<tr><td><code>xds_cache_evictions</code></td><td><code>Sum</code></td><td>Total number of xds cache evictions.</td></tr>
<tr><td><code>xds_cache_reads</code></td><td><code>Sum</code></td><td>Total number of xds cache xdsCacheReads.</td></tr>
<tr><td><code>xds_cache_size</code></td><td><code>LastValue</code></td><td>Current size of xds cache</td></tr>
</tbody>
</table>