---
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: install-cni
description: Install and configure Istio CNI plugin on a node, detect and repair pod which is broken by race condition.
generator: pkg-collateral-docs
number_of_entries: 8
max_toc_level: 2
remove_toc_prefix: 'install-cni '
---
<p>Install and configure Istio CNI plugin on a node, detect and repair pod which is broken by race condition.</p>
<pre class="language-bash"><code>install-cni [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--chained-cni-plugin</code></td>
<td>Whether to install CNI plugin as a chained or standalone </td>
</tr>
<tr>
<td><code>--cni-conf-name &lt;string&gt;</code></td>
<td>Name of the CNI configuration file  (default ``)</td>
</tr>
<tr>
<td><code>--cni-enable-install</code></td>
<td>Whether to install CNI configuration and binary files </td>
</tr>
<tr>
<td><code>--cni-enable-reinstall</code></td>
<td>Whether to reinstall CNI configuration and binary files </td>
</tr>
<tr>
<td><code>--cni-net-dir &lt;string&gt;</code></td>
<td>Directory on the host where CNI network plugins are installed  (default `/etc/cni/net.d`)</td>
</tr>
<tr>
<td><code>--cni-network-config &lt;string&gt;</code></td>
<td>CNI configuration template as a string  (default ``)</td>
</tr>
<tr>
<td><code>--cni-network-config-file &lt;string&gt;</code></td>
<td>CNI config template as a file  (default ``)</td>
</tr>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--kube-ca-file &lt;string&gt;</code></td>
<td>CA file for kubeconfig. Defaults to the same as install-cni pod  (default ``)</td>
</tr>
<tr>
<td><code>--kubecfg-file-name &lt;string&gt;</code></td>
<td>Name of the kubeconfig file which CNI plugin will use when interacting with API server  (default `ZZZ-istio-cni-kubeconfig`)</td>
</tr>
<tr>
<td><code>--kubeconfig-mode &lt;int&gt;</code></td>
<td>File mode of the kubeconfig file  (default `384`)</td>
</tr>
<tr>
<td><code>--log-level &lt;string&gt;</code></td>
<td>Fallback value for log level in CNI config file, if not specified in helm template  (default `warn`)</td>
</tr>
<tr>
<td><code>--log-uds-address &lt;string&gt;</code></td>
<td>The UDS server address which CNI plugin will copy log ouptut to  (default `/var/run/istio-cni/log.sock`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
<tr>
<td><code>--monitoring-port &lt;int&gt;</code></td>
<td>HTTP port to serve prometheus metrics  (default `15014`)</td>
</tr>
<tr>
<td><code>--mounted-cni-net-dir &lt;string&gt;</code></td>
<td>Directory on the container where CNI networks are installed  (default `/host/etc/cni/net.d`)</td>
</tr>
<tr>
<td><code>--repair-broken-pod-label-key &lt;string&gt;</code></td>
<td>The key portion of the label which will be set by the ace repair if label pods is true  (default `cni.istio.io/uninitialized`)</td>
</tr>
<tr>
<td><code>--repair-broken-pod-label-value &lt;string&gt;</code></td>
<td>The value portion of the label which will be set by the race repair if label pods is true  (default `true`)</td>
</tr>
<tr>
<td><code>--repair-delete-pods</code></td>
<td>Controller will delete pods when detecting pod broken by race condition </td>
</tr>
<tr>
<td><code>--repair-enabled</code></td>
<td>Whether to enable race condition repair or not </td>
</tr>
<tr>
<td><code>--repair-field-selectors &lt;string&gt;</code></td>
<td>A set of field selectors in label=value format that will be added to the pod list filters  (default ``)</td>
</tr>
<tr>
<td><code>--repair-init-container-exit-code &lt;int&gt;</code></td>
<td>Expected exit code for the init container when crash-looping because of CNI misconfiguration  (default `126`)</td>
</tr>
<tr>
<td><code>--repair-init-container-name &lt;string&gt;</code></td>
<td>The name of the istio init container (will crash-loop if CNI is not configured for the pod)  (default `istio-validation`)</td>
</tr>
<tr>
<td><code>--repair-init-container-termination-message &lt;string&gt;</code></td>
<td>The expected termination message for the init container when crash-looping because of CNI misconfiguration  (default ``)</td>
</tr>
<tr>
<td><code>--repair-label-pods</code></td>
<td>Controller will label pods when detecting pod broken by race condition </td>
</tr>
<tr>
<td><code>--repair-label-selectors &lt;string&gt;</code></td>
<td>A set of label selectors in label=value format that will be added to the pod list filters  (default ``)</td>
</tr>
<tr>
<td><code>--repair-node-name &lt;string&gt;</code></td>
<td>The name of the managed node (will manage all nodes if unset)  (default ``)</td>
</tr>
<tr>
<td><code>--repair-run-as-daemon</code></td>
<td>Controller will run in a loop </td>
</tr>
<tr>
<td><code>--repair-sidecar-annotation &lt;string&gt;</code></td>
<td>An annotation key that indicates this pod contains an istio sidecar. All pods without this annotation will be ignored.The value of the annotation is ignored.  (default `sidecar.istio.io/status`)</td>
</tr>
<tr>
<td><code>--skip-cni-binaries &lt;istio-cni&gt;</code></td>
<td>Binaries that should not be installed. Currently Istio only installs one binary istio-cni  (default `[]`)</td>
</tr>
<tr>
<td><code>--skip-tls-verify</code></td>
<td>Whether to use insecure TLS in kubeconfig file </td>
</tr>
<tr>
<td><code>--update-cni-binaries</code></td>
<td>Whether to refresh existing binaries when installing CNI </td>
</tr>
</tbody>
</table>
<h2 id="install-cni-completion">install-cni completion</h2>
<p>Generate the autocompletion script for install-cni 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>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
</tbody>
</table>
<h2 id="install-cni-completion-bash">install-cni 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;(install-cni completion bash)</p>
<p>To load completions for every new session, execute once:</p>
<p>#### Linux:</p>
<p>	install-cni completion bash &gt; /etc/bash_completion.d/install-cni</p>
<p>#### macOS:</p>
<p>	install-cni completion bash &gt; $(brew --prefix)/etc/bash_completion.d/install-cni</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>install-cni completion bash
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td>disable completion descriptions </td>
</tr>
</tbody>
</table>
<h2 id="install-cni-completion-fish">install-cni completion fish</h2>
<p>Generate the autocompletion script for the fish shell.</p>
<p>To load completions in your current shell session:</p>
<p>	install-cni completion fish | source</p>
<p>To load completions for every new session, execute once:</p>
<p>	install-cni completion fish &gt; ~/.config/fish/completions/install-cni.fish</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>install-cni completion fish [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td>disable completion descriptions </td>
</tr>
</tbody>
</table>
<h2 id="install-cni-completion-powershell">install-cni completion powershell</h2>
<p>Generate the autocompletion script for powershell.</p>
<p>To load completions in your current shell session:</p>
<p>	install-cni 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>install-cni completion powershell [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td>disable completion descriptions </td>
</tr>
</tbody>
</table>
<h2 id="install-cni-completion-zsh">install-cni 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;(install-cni completion zsh); compdef _install-cni install-cni</p>
<p>To load completions for every new session, execute once:</p>
<p>#### Linux:</p>
<p>	install-cni completion zsh &gt; &#34;${fpath[1]}/_install-cni&#34;</p>
<p>#### macOS:</p>
<p>	install-cni completion zsh &gt; $(brew --prefix)/share/zsh/site-functions/_install-cni</p>
<p>You will need to start a new shell for this setup to take effect.
</p>
<pre class="language-bash"><code>install-cni completion zsh [flags]
</code></pre>
<table class="command-flags">
<thead>
<tr>
<th>Flags</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>--ctrlz_address &lt;string&gt;</code></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</td>
</tr>
<tr>
<td><code>--no-descriptions</code></td>
<td>disable completion descriptions </td>
</tr>
</tbody>
</table>
<h2 id="install-cni-version">install-cni version</h2>
<p>Prints out build version information</p>
<pre class="language-bash"><code>install-cni 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>--ctrlz_address &lt;string&gt;</code></td>
<td></td>
<td>The IP Address to listen on for the ControlZ introspection facility. Use &#39;*&#39; to indicate all addresses.  (default `localhost`)</td>
</tr>
<tr>
<td><code>--ctrlz_port &lt;uint16&gt;</code></td>
<td></td>
<td>The IP port to use for the ControlZ introspection facility  (default `9876`)</td>
</tr>
<tr>
<td><code>--log_as_json</code></td>
<td></td>
<td>Whether to format output as JSON or in plain console-friendly format </td>
</tr>
<tr>
<td><code>--log_caller &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated list of scopes for which to include caller information, scopes can be any of [all, cni, default, install, klog, repair]  (default ``)</td>
</tr>
<tr>
<td><code>--log_output_level &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:info`)</td>
</tr>
<tr>
<td><code>--log_rotate &lt;string&gt;</code></td>
<td></td>
<td>The path for the optional rotating log file  (default ``)</td>
</tr>
<tr>
<td><code>--log_rotate_max_age &lt;int&gt;</code></td>
<td></td>
<td>The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit)  (default `30`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_backups &lt;int&gt;</code></td>
<td></td>
<td>The maximum number of log file backups to keep before older files are deleted (0 indicates no limit)  (default `1000`)</td>
</tr>
<tr>
<td><code>--log_rotate_max_size &lt;int&gt;</code></td>
<td></td>
<td>The maximum size in megabytes of a log file beyond which the file is rotated  (default `104857600`)</td>
</tr>
<tr>
<td><code>--log_stacktrace_level &lt;string&gt;</code></td>
<td></td>
<td>Comma-separated minimum per-scope logging level at which stack traces are captured, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope:level&gt;,... where scope can be one of [all, cni, default, install, klog, repair] and level can be one of [debug, info, warn, error, fatal, none]  (default `default:none`)</td>
</tr>
<tr>
<td><code>--log_target &lt;stringArray&gt;</code></td>
<td></td>
<td>The set of paths where to output the log. This can be any path as well as the special values stdout and stderr  (default `[stdout]`)</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>
</tbody>
</table>
<h2 id="envvars">Environment variables</h2>
These environment variables affect the behavior of the <code>install-cni</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>CHAINED_CNI_PLUGIN</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Whether to install CNI plugin as a chained or standalone</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>CNI_CONF_NAME</code></td>
<td>String</td>
<td><code></code></td>
<td>Name of the CNI configuration file</td>
</tr>
<tr>
<td><code>CNI_ENABLE_INSTALL</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Whether to install CNI configuration and binary files</td>
</tr>
<tr>
<td><code>CNI_ENABLE_REINSTALL</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Whether to reinstall CNI configuration and binary files</td>
</tr>
<tr>
<td><code>CNI_NETWORK_CONFIG</code></td>
<td>String</td>
<td><code></code></td>
<td>CNI configuration template as a string</td>
</tr>
<tr>
<td><code>CNI_NETWORK_CONFIG_FILE</code></td>
<td>String</td>
<td><code></code></td>
<td>CNI config template as a file</td>
</tr>
<tr>
<td><code>CNI_NET_DIR</code></td>
<td>String</td>
<td><code>/etc/cni/net.d</code></td>
<td>Directory on the host where CNI network plugins are installed</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_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>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>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_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. Deprecated: in Istio 1.15+ port is ignored in domain matching.</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_OUTBOUND_OWNER_GROUPS</code></td>
<td>String</td>
<td><code>*</code></td>
<td>Comma separated list of groups whose outgoing traffic is to be redirected to Envoy.
A group can be specified either by name or by a numeric GID.
The wildcard character &#34;*&#34; can be used to configure redirection of traffic from all groups.</td>
</tr>
<tr>
<td><code>ISTIO_OUTBOUND_OWNER_GROUPS_EXCLUDE</code></td>
<td>String</td>
<td><code></code></td>
<td>Comma separated list of groups whose outgoing traffic is to be excluded from redirection to Envoy.
A group can be specified either by name or by a numeric GID.
Only applies when traffic from all groups (i.e. &#34;*&#34;) is being redirected to Envoy.</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>KUBECFG_FILE_NAME</code></td>
<td>String</td>
<td><code>ZZZ-istio-cni-kubeconfig</code></td>
<td>Name of the kubeconfig file which CNI plugin will use when interacting with API server</td>
</tr>
<tr>
<td><code>KUBECONFIG_MODE</code></td>
<td>Integer</td>
<td><code>384</code></td>
<td>File mode of the kubeconfig file</td>
</tr>
<tr>
<td><code>KUBE_CA_FILE</code></td>
<td>String</td>
<td><code></code></td>
<td>CA file for kubeconfig. Defaults to the same as install-cni pod</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>LOG_LEVEL</code></td>
<td>String</td>
<td><code>warn</code></td>
<td>Fallback value for log level in CNI config file, if not specified in helm template</td>
</tr>
<tr>
<td><code>LOG_UDS_ADDRESS</code></td>
<td>String</td>
<td><code>/var/run/istio-cni/log.sock</code></td>
<td>The UDS server address which CNI plugin will copy log ouptut to</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>MONITORING_PORT</code></td>
<td>Integer</td>
<td><code>15014</code></td>
<td>HTTP port to serve prometheus metrics</td>
</tr>
<tr>
<td><code>MOUNTED_CNI_NET_DIR</code></td>
<td>String</td>
<td><code>/host/etc/cni/net.d</code></td>
<td>Directory on the container where CNI networks are installed</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>false</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_K8S_SELECT_WORKLOAD_ENTRIES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, Kubernetes services with selectors will select workload entries with matching labels. 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_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_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>Integer</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>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>REPAIR_BROKEN_POD_LABEL_KEY</code></td>
<td>String</td>
<td><code>cni.istio.io/uninitialized</code></td>
<td>The key portion of the label which will be set by the ace repair if label pods is true</td>
</tr>
<tr>
<td><code>REPAIR_BROKEN_POD_LABEL_VALUE</code></td>
<td>String</td>
<td><code>true</code></td>
<td>The value portion of the label which will be set by the race repair if label pods is true</td>
</tr>
<tr>
<td><code>REPAIR_DELETE_PODS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Controller will delete pods when detecting pod broken by race condition</td>
</tr>
<tr>
<td><code>REPAIR_ENABLED</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Whether to enable race condition repair or not</td>
</tr>
<tr>
<td><code>REPAIR_FIELD_SELECTORS</code></td>
<td>String</td>
<td><code></code></td>
<td>A set of field selectors in label=value format that will be added to the pod list filters</td>
</tr>
<tr>
<td><code>REPAIR_INIT_CONTAINER_EXIT_CODE</code></td>
<td>Integer</td>
<td><code>126</code></td>
<td>Expected exit code for the init container when crash-looping because of CNI misconfiguration</td>
</tr>
<tr>
<td><code>REPAIR_INIT_CONTAINER_NAME</code></td>
<td>String</td>
<td><code>istio-validation</code></td>
<td>The name of the istio init container (will crash-loop if CNI is not configured for the pod)</td>
</tr>
<tr>
<td><code>REPAIR_INIT_CONTAINER_TERMINATION_MESSAGE</code></td>
<td>String</td>
<td><code></code></td>
<td>The expected termination message for the init container when crash-looping because of CNI misconfiguration</td>
</tr>
<tr>
<td><code>REPAIR_LABEL_PODS</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Controller will label pods when detecting pod broken by race condition</td>
</tr>
<tr>
<td><code>REPAIR_LABEL_SELECTORS</code></td>
<td>String</td>
<td><code></code></td>
<td>A set of label selectors in label=value format that will be added to the pod list filters</td>
</tr>
<tr>
<td><code>REPAIR_NODE_NAME</code></td>
<td>String</td>
<td><code></code></td>
<td>The name of the managed node (will manage all nodes if unset)</td>
</tr>
<tr>
<td><code>REPAIR_RUN_AS_DAEMON</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Controller will run in a loop</td>
</tr>
<tr>
<td><code>REPAIR_SIDECAR_ANNOTATION</code></td>
<td>String</td>
<td><code>sidecar.istio.io/status</code></td>
<td>An annotation key that indicates this pod contains an istio sidecar. All pods without this annotation will be ignored.The value of the annotation is ignored.</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_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>SIDECAR_IGNORE_PORT_IN_HOST_MATCH</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>If enabled, port will not be used in vhost domain matches.</td>
</tr>
<tr>
<td><code>SKIP_CNI_BINARIES</code></td>
<td>String</td>
<td><code></code></td>
<td>Binaries that should not be installed. Currently Istio only installs one binary `istio-cni`</td>
</tr>
<tr>
<td><code>SKIP_TLS_VERIFY</code></td>
<td>Boolean</td>
<td><code>false</code></td>
<td>Whether to use insecure TLS in kubeconfig file</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>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 authentication 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>UPDATE_CNI_BINARIES</code></td>
<td>Boolean</td>
<td><code>true</code></td>
<td>Whether to refresh existing binaries when installing CNI</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>
</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>istio_build</code></td><td><code>LastValue</code></td><td>Istio component build info</td></tr>
<tr><td><code>istio_cni_install_ready</code></td><td><code>LastValue</code></td><td>Whether the CNI plugin installation is ready or not</td></tr>
<tr><td><code>istio_cni_installs_total</code></td><td><code>Sum</code></td><td>Total number of CNI plugins installed by the Istio CNI installer</td></tr>
<tr><td><code>istio_cni_repair_pods_repaired_total</code></td><td><code>Sum</code></td><td>Total number of pods repaired by repair controller</td></tr>
</tbody>
</table>