istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
istio.io/archive/v1.16/zh/docs/reference/commands/istioctl/index.html

951 lines
356 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!doctype html><html lang=zh itemscope itemtype=https://schema.org/WebPage><head><meta charset=utf-8><meta http-equiv=x-ua-compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta name=theme-color content="#466BB0"><meta name=title content="istioctl"><meta name=description content="Istio control interface."><meta name=keywords content="microservices,services,mesh"><meta property="og:title" content="istioctl"><meta property="og:type" content="website"><meta property="og:description" content="Istio control interface."><meta property="og:url" content="/v1.16/zh/docs/reference/commands/istioctl/"><meta property="og:image" content="https://raw.githubusercontent.com/istio/istio.io/master/static/img/istio-social.svg"><meta property="og:image:alt" content="Istio Logo"><meta property="og:image:width" content="1200"><meta property="og:image:height" content="600"><meta property="og:site_name" content="Istio"><meta name=twitter:card content="summary"><meta name=twitter:site content="@IstioMesh"><title>Istioldie 1.16 / istioctl</title><script async src="https://www.googletagmanager.com/gtag/js?id=UA-98480406-2"></script>
<script>window.dataLayer=window.dataLayer||[];function gtag(){dataLayer.push(arguments)}gtag("js",new Date),gtag("config","UA-98480406-2")</script><link rel=alternate type=application/rss+xml title="Istio Blog" href=/v1.16/blog/feed.xml><link rel=alternate type=application/rss+xml title="Istio News" href=/v1.16/news/feed.xml><link rel=alternate type=application/rss+xml title="Istio Blog and News" href=/v1.16/feed.xml><link rel="shortcut icon" href=/v1.16/favicons/favicon.ico><link rel=apple-touch-icon href=/v1.16/favicons/apple-touch-icon-180x180.png sizes=180x180><link rel=icon type=image/png href=/v1.16/favicons/favicon-16x16.png sizes=16x16><link rel=icon type=image/png href=/v1.16/favicons/favicon-32x32.png sizes=32x32><link rel=icon type=image/png href=/v1.16/favicons/android-36x36.png sizes=36x36><link rel=icon type=image/png href=/v1.16/favicons/android-48x48.png sizes=48x48><link rel=icon type=image/png href=/v1.16/favicons/android-72x72.png sizes=72x72><link rel=icon type=image/png href=/v1.16/favicons/android-96x96.png sizes=96xW96><link rel=icon type=image/png href=/v1.16/favicons/android-144x144.png sizes=144x144><link rel=icon type=image/png href=/v1.16/favicons/android-192x192.png sizes=192x192><link rel=icon type=image/svg+xml href=/v1.16/favicons/favicon.svg><link rel=icon type=image/png href=/v1.16/favicons/favicon.png><link rel=mask-icon href=/v1.16/favicons/safari-pinned-tab.svg color=#466bb0><link rel=manifest href=/v1.16/manifest.json><meta name=apple-mobile-web-app-title content="Istio"><meta name=application-name content="Istio"><meta name=msapplication-config content="/browserconfig.xml"><meta name=msapplication-TileColor content="#466BB0"><meta name=theme-color content="#466BB0"><link rel=stylesheet href=/v1.16/css/all.css><link rel=preconnect href=https://fonts.googleapis.com><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link rel=stylesheet href="https://fonts.googleapis.com/css2?family=Barlow:ital,wght@0,400;0,500;0,600;0,700;1,400;1,600&display=swap"><script src=/v1.16/js/themes_init.min.js></script></head><body class="language-unknown archive-site"><script>const branchName="release-1.16",docTitle="istioctl",iconFile="/v1.16/img/icons.svg",buttonCopy="复制到剪切板",buttonPrint="打印",buttonDownload="下载"</script><script src="https://www.google.com/cse/brand?form=search-form" defer></script>
<script src=/v1.16/js/all.min.js data-manual defer></script><header class=main-navigation><nav class="main-navigation-wrapper container-l"><div class=main-navigation-header><a id=brand href=/v1.16/zh/ aria-label=logotype><span class=logo><svg xmlns="http://www.w3.org/2000/svg" width="128" height="60" viewBox="0 0 128 60"><path d="M58.434 48.823A.441.441.0 0158.3 48.497V22.583a.444.444.0 01.134-.326.446.446.0 01.327-.134h3.527a.447.447.0 01.325.134.447.447.0 01.134.326v25.914a.443.443.0 01-.134.326.444.444.0 01-.325.134h-3.527a.444.444.0 01-.327-.134z"/><path d="m70.969 48.477a6.556 6.556.0 01-2.818-1.955 4.338 4.338.0 01-1-2.78v-.345a.443.443.0 01.134-.326.444.444.0 01.326-.135h3.374a.444.444.0 01.326.135.445.445.0 01.134.326v.077a2.014 2.014.0 001.054 1.667 4.672 4.672.0 002.664.709 4.446 4.446.0 002.492-.633 1.862 1.862.0 00.958-1.591 1.426 1.426.0 00-.786-1.322 12.7 12.7.0 00-2.549-.939l-1.457-.46a21.526 21.526.0 01-3.3-1.227 6.57 6.57.0 01-2.262-1.783 4.435 4.435.0 01-.92-2.894 5.081 5.081.0 012.109-4.275 8.993 8.993.0 015.558-1.591 10.445 10.445.0 014.1.748 6.3 6.3.0 012.722 2.07 5 5 0 01.958 3.009.441.441.0 01-.134.326.441.441.0 01-.325.134h-3.258a.441.441.0 01-.326-.134.443.443.0 01-.134-.326 1.974 1.974.0 00-.978-1.667 4.647 4.647.0 00-2.665-.671 4.741 4.741.0 00-2.435.556 1.724 1.724.0 00-.938 1.553 1.512 1.512.0 00.9 1.4 15.875 15.875.0 003.01 1.055l.843.229a27.368 27.368.0 013.412 1.246 6.67 6.67.0 012.338 1.763 4.387 4.387.0 01.958 2.933 4.988 4.988.0 01-2.146 4.275 9.543 9.543.0 01-5.712 1.552 11.626 11.626.0 01-4.227-.709z"/><path d="m97.039 32.837a.443.443.0 01-.326.135h-3.911a.169.169.0 00-.191.192v9.239a2.951 2.951.0 00.632 2.108 2.7 2.7.0 002.013.652h1.15a.444.444.0 01.325.134.441.441.0 01.134.326v2.875a.471.471.0 01-.459.5l-1.994.039a8 8 0 01-4.524-1.035q-1.495-1.035-1.533-3.91V33.166A.17.17.0 0088.164 32.974H85.978A.441.441.0 0185.652 32.839.441.441.0 0185.518 32.513V29.83a.441.441.0 01.134-.326.444.444.0 01.326-.135h2.186a.169.169.0 00.191-.192v-4.485a.438.438.0 01.134-.326.44.44.0 01.325-.134h3.336a.443.443.0 01.325.134.442.442.0 01.135.326v4.485a.169.169.0 00.191.192h3.911a.446.446.0 01.326.135.446.446.0 01.134.326v2.683a.446.446.0 01-.133.324z"/><path d="m101.694 25.917a2.645 2.645.0 01-.767-1.955 2.65 2.65.0 01.767-1.955 2.65 2.65.0 011.955-.767 2.65 2.65.0 011.955.767 2.652 2.652.0 01.767 1.955 2.647 2.647.0 01-.767 1.955 2.646 2.646.0 01-1.955.767 2.645 2.645.0 01-1.955-.767zm-.211 22.906a.441.441.0 01-.134-.326V29.79a.444.444.0 01.134-.326.446.446.0 01.326-.134h3.527a.446.446.0 01.326.134.445.445.0 01.134.326v18.707a.443.443.0 01-.134.326.443.443.0 01-.326.134h-3.527a.443.443.0 01-.326-.134z"/><path d="m114.019 47.734a8.1 8.1.0 01-3.047-4.255 14.439 14.439.0 01-.652-4.37 14.3 14.3.0 01.614-4.371A7.869 7.869.0 01114 30.56a9.072 9.072.0 015.252-1.5 8.543 8.543.0 015.041 1.5 7.985 7.985.0 013.009 4.14 12.439 12.439.0 01.69 4.37 13.793 13.793.0 01-.651 4.37 8.255 8.255.0 01-3.028 4.275 8.475 8.475.0 01-5.1 1.553 8.754 8.754.0 01-5.194-1.534zm7.629-3.1a4.536 4.536.0 001.476-2.262 11.335 11.335.0 00.383-3.221 10.618 10.618.0 00-.383-3.22 4.169 4.169.0 00-1.457-2.243 4.066 4.066.0 00-2.531-.785 3.942 3.942.0 00-2.453.785 4.376 4.376.0 00-1.5 2.243 11.839 11.839.0 00-.383 3.22 11.84 11.84.0 00.383 3.221 4.222 4.222.0 001.476 2.262 4.075 4.075.0 002.549.8 3.8 3.8.0 002.44-.809z"/><path d="m15.105 32.057v15.565a.059.059.0 01-.049.059L.069 50.25A.06.06.0 01.005 50.167l14.987-33.47a.06.06.0 01.114.025z"/><path d="m17.631 23.087v24.6a.06.06.0 00.053.059l22.449 2.507a.06.06.0 00.061-.084L17.745.032a.06.06.0 00-.114.024z"/><path d="m39.961 52.548-24.833 7.45a.062.062.0 01-.043.0L.079 52.548a.059.059.0 01.026-.113h39.839a.06.06.0 01.017.113z"/></svg></span></a><button id=hamburger class=main-navigation-toggle aria-label="Open navigation"><svg class="icon menu-hamburger"><use xlink:href="/v1.16/img/icons.svg#menu-hamburger"/></svg></button>
<button id=menu-close class=main-navigation-toggle aria-label="Close navigation"><svg class="icon menu-close"><use xlink:href="/v1.16/img/icons.svg#menu-close"/></svg></button></div><div id=header-links class=main-navigation-links-wrapper><ul class=main-navigation-links><li class=main-navigation-links-item><a class="main-navigation-links-link has-dropdown"><span>关于</span><svg class="icon dropdown-arrow"><use xlink:href="/v1.16/img/icons.svg#dropdown-arrow"/></svg></a><ul class=main-navigation-links-dropdown><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/service-mesh class=main-navigation-links-link>服务网格</a></li><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/solutions class=main-navigation-links-link>解决方案</a></li><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/case-studies class=main-navigation-links-link>案例学习</a></li><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/ecosystem class=main-navigation-links-link>生态系统</a></li><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/deployment class=main-navigation-links-link>部署</a></li><li class=main-navigation-links-dropdown-item><a href=/v1.16/zh/about/faq class=main-navigation-links-link>FAQ</a></li></ul></li><li class=main-navigation-links-item><a href=/v1.16/zh/blog/ class=main-navigation-links-link><span>博客</span></a></li><li class=main-navigation-links-item><a href=/v1.16/zh/news/ class=main-navigation-links-link><span>新闻</span></a></li><li class=main-navigation-links-item><a href=/v1.16/zh/get-involved/ class=main-navigation-links-link><span>加入我们</span></a></li><li class=main-navigation-links-item><a href=/v1.16/zh/docs/ class=main-navigation-links-link><span>文档</span></a></li></ul><div class=main-navigation-footer><button id=search-show class=search-show title='搜索 istio.io' aria-label=搜索><svg class="icon magnifier"><use xlink:href="/v1.16/img/icons.svg#magnifier"/></svg></button>
<a href=/v1.16/zh/docs/setup/getting-started class="btn btn--primary" id=try-istio>试用 Istio</a></div></div><form id=search-form class=search name=cse role=search><input type=hidden name=cx value=002184991200833970123:iwwf17ikgf4>
<input type=hidden name=ie value=utf-8>
<input type=hidden name=hl value=zh>
<input type=hidden id=search-page-url value=/zh/search>
<input id=search-textbox class="search-textbox form-control" name=q type=search aria-label='搜索 istio.io' placeholder=搜索>
<button id=search-close title=取消搜索 type=reset aria-label=取消搜索><svg class="icon menu-close"><use xlink:href="/v1.16/img/icons.svg#menu-close"/></svg></button></form></nav></header><div class=banner-container></div><main class="primary container has-sidebar has-toc docs"><div id=sidebar-container class=sidebar-container><nav id=sidebar aria-label="Section Navigation"><button id=sidebar-close class="main-navigation-toggle sidebar-close" aria-label="Close sidebar"><svg class="icon menu-close"><use xlink:href="/v1.16/img/icons.svg#menu-close"/></svg></button><div class=sidebar-nav><div class=search><form id=search-docs-form name=cse role=search><input type=hidden name=ie value=utf-8>
<input type=hidden name=hl value=en>
<input type=hidden id=search-docs-url value=/v1.16/search>
<input id=search-docs-textbox class=form-control name=docs-search type=search aria-label='搜索 istio.io' placeholder=搜索>
<button id=search-show2 class=search-show title='搜索 istio.io' aria-label=搜索><svg class="icon magnifier"><use xlink:href="/v1.16/img/icons.svg#magnifier"/></svg></button></form></div><div class=card><div class="body default" aria-labelledby=header0><ul role=tree aria-expanded=true aria-labelledby=header0><li role=treeitem aria-label=概念><a class=main title="一些概念，理解它们有助于您更好地了解 Istio 系统的不同部分及其使用的抽象。" href=/v1.16/zh/docs/concepts/>概念</a><ul role=group aria-expanded=true class=leaf-section><li role=none><a role=treeitem title="描述 Istio 多样的流量路由和控制特性。" href=/v1.16/zh/docs/concepts/traffic-management/>流量管理</a></li><li role=none><a role=treeitem title="讲述 Istio 的 WebAssembly 插件系统。" href=/v1.16/zh/docs/concepts/wasm/>扩展性</a></li><li role=none><a role=treeitem title="描述 Istio 的授权与认证功能。" href=/v1.16/zh/docs/concepts/security/>安全</a></li><li role=none><a role=treeitem title="描述 Istio 提供的遥测和监控特性。" href=/v1.16/zh/docs/concepts/observability/>可观测性</a></li></ul></li><li role=treeitem aria-label=安装><a class=main title="关于如何在 Kubernetes 集群中安装 Istio 控制平面和添加虚拟机到 mesh 中的说明。" href=/v1.16/zh/docs/setup/>安装</a><ul role=group aria-expanded=true><li role=none><a role=treeitem title="快速、轻松地尝试 Istio 特性。" href=/v1.16/zh/docs/setup/getting-started/>入门</a></li><li role=treeitem aria-label=平台安装><button aria-hidden=true tabindex=-1></button><a title="在安装 Istio 之前如何准备各种 Kubernetes 平台。" href=/v1.16/zh/docs/setup/platform-setup/>平台安装</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="在各平台上安装 Istio 的前提条件。" href=/v1.16/zh/docs/setup/platform-setup/prerequisites/>平台前提条件</a></li><li role=none><a role=treeitem title="在阿里云 Kubernetes 集群进行配置以便安装运行 Istio。" href=/v1.16/zh/docs/setup/platform-setup/alicloud/>阿里云</a></li><li role=none><a role=treeitem title="为 Istio 设置一个 Azure 集群的操作说明。" href=/v1.16/zh/docs/setup/platform-setup/azure/>Azure</a></li><li role=none><a role=treeitem title="在 Docker Desktop 中运行 Istio 的设置说明。" href=/v1.16/zh/docs/setup/platform-setup/docker/>Docker Desktop</a></li><li role=none><a role=treeitem title="为 Istio 设置 kind 的说明。" href=/v1.16/zh/docs/setup/platform-setup/kind/>kind</a></li><li role=none><a role=treeitem title="在 Google Kubernetes Engine (GKE) 上快速搭建 Istio 服务。" href=/v1.16/zh/docs/setup/platform-setup/gke/>使用 Google Kubernetes Engine 快速开始</a></li><li role=none><a role=treeitem title="在 Minikube 上配置 Istio。" href=/v1.16/zh/docs/setup/platform-setup/minikube/>Minikube</a></li><li role=none><a role=treeitem title="为 Istio 设置一个华为云 Kubernetes 集群的操作说明。" href=/v1.16/zh/docs/setup/platform-setup/huaweicloud/>华为云</a></li><li role=none><a role=treeitem title="在 IBM 公有云或私有云上快速搭建 Istio 服务。" href=/v1.16/zh/docs/setup/platform-setup/ibm/>IBM Cloud 快速开始</a></li><li role=none><a role=treeitem title="与Istio 一起使用的 Kops 设置说明。" href=/v1.16/zh/docs/setup/platform-setup/kops/>Kops</a></li><li role=none><a role=treeitem title="使用 Gardener 快速搭建 Istio 服务。" href=/v1.16/zh/docs/setup/platform-setup/gardener/>Kubernetes Gardener 快速开始</a></li><li role=none><a role=treeitem title="Istio 适配 KubeSphere 容器平台指南。" href=/v1.16/zh/docs/setup/platform-setup/kubesphere/>KubeSphere Container Platform</a></li><li role=none><a role=treeitem title="配置 MicroK8s 以便使用 Istio。" href=/v1.16/zh/docs/setup/platform-setup/microk8s/>MicroK8s</a></li><li role=none><a role=treeitem title="在 OpenShift 集群上快速搭建 Istio 服务。" href=/v1.16/zh/docs/setup/platform-setup/openshift/>OpenShift</a></li><li role=none><a role=treeitem title="使用 Oracle Container 为 Istio 准备集群的说明。" href=/v1.16/zh/docs/setup/platform-setup/oci/>Oracle Cloud 基础架构</a></li><li role=none><a role=treeitem title="在腾讯云上快速创建 Istio 服务。" href=/v1.16/zh/docs/setup/platform-setup/tencent-cloud-mesh/>腾讯云</a></li></ul></li><li role=treeitem aria-label=安装><button aria-hidden=true tabindex=-1></button><a title=选择最适合你需求和平台的安装指南。 href=/v1.16/zh/docs/setup/install/>安装</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title="安装、定制 Istio 配置文件，用于深入评估及生产发布。" href=/v1.16/zh/docs/setup/install/istioctl/>使用 Istioctl 安装</a></li><li role=none><a role=treeitem title="安装、配置并深入评估 Istio。" href=/v1.16/zh/docs/setup/install/helm/>使用 Helm 安装</a></li><li role=treeitem aria-label=多集群安装><button aria-hidden=true tabindex=-1></button><a title="跨多 Kubernetes 集群，安装 Istio 服务网格。" href=/v1.16/zh/docs/setup/install/multicluster/>多集群安装</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="在多个集群上安装 Istio 之前的初始步骤。" href=/v1.16/zh/docs/setup/install/multicluster/before-you-begin/>准备工作</a></li><li role=none><a role=treeitem title="跨多个主集群，安装 Istio 网格。" href=/v1.16/zh/docs/setup/install/multicluster/multi-primary/>多主架构的安装</a></li><li role=none><a role=treeitem title="跨主-从集群，安装 Istio 网格。" href=/v1.16/zh/docs/setup/install/multicluster/primary-remote/>主-从架构的安装</a></li><li role=none><a role=treeitem title="跨网络、多主架构的 Istio 网格安装。" href=/v1.16/zh/docs/setup/install/multicluster/multi-primary_multi-network/>跨网络多主架构的安装</a></li><li role=none><a role=treeitem title="跨网络、主-从架构的 Istio 网格安装。" href=/v1.16/zh/docs/setup/install/multicluster/primary-remote_multi-network/>跨网络主-从架构的安装</a></li><li role=none><a role=treeitem title="验证 Istio 已成功安装到多集群环境中。" href=/v1.16/zh/docs/setup/install/multicluster/verify/>验证安装结果</a></li></ul></li><li role=none><a role=treeitem title="部署 Istio，接入虚拟机中运行的工作负载。" href=/v1.16/zh/docs/setup/install/virtual-machine/>虚拟机安装</a></li><li role=none><a role=treeitem title="使用修订和 discoverySelectors 在单集群中安装多个 Istio 控制面。" href=/v1.16/zh/docs/setup/install/multiple-controlplanes/>在单集群中安装多个 Istio 控制面</a></li><li role=none><a role=treeitem title=安装外部控制平面和远程集群。 href=/v1.16/zh/docs/setup/install/external-controlplane/>使用外部控制平面安装 Istio</a></li><li role=none><a role=treeitem title="使用 Istio Operator 在 Kubernetes 集群中安装 Istio 的说明。 (Beta)" href=/v1.16/zh/docs/setup/install/operator/>使用 Istio Operator 安装 *</a></li></ul></li><li role=treeitem aria-label=升级><button aria-hidden=true tabindex=-1></button><a title="跨多个控制平面升级、降级和管理 Istio。" href=/v1.16/zh/docs/setup/upgrade/>升级</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="通过先运行一个金丝雀部署的新控制平面升级 Istio。" href=/v1.16/zh/docs/setup/upgrade/canary/>金丝雀升级</a></li><li role=none><a role=treeitem title=原地升级和回退。 href=/v1.16/zh/docs/setup/upgrade/in-place/>原地升级</a></li><li role=none><a role=treeitem title="深度评估升级和配置 Istio。" href=/v1.16/zh/docs/setup/upgrade/helm/>Upgrade with Helm</a></li></ul></li><li role=treeitem aria-label=更多指南><button aria-hidden=true tabindex=-1></button><a title=有关其他设置任务的更多信息。 href=/v1.16/zh/docs/setup/additional-setup/>更多指南</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述 Istio 内置的安装配置文件。" href=/v1.16/zh/docs/setup/additional-setup/config-profiles/>安装配置文件</a></li><li role=none><a role=treeitem title="在应用程序 Pod 中使用 Sidecar Injector Webhook 自动安装或使用 Istioctl CLI 手动安装 Istio Sidecar。" href=/v1.16/zh/docs/setup/additional-setup/sidecar-injection/>安装 Sidecar</a></li><li role=none><a role=treeitem title=描述如何定制安装配置选项。 href=/v1.16/zh/docs/setup/additional-setup/customize-installation/>定制安装配置</a></li><li role=none><a role=treeitem title="描述使用 helm 安装时如何自定义安装配置选项。" href=/v1.16/zh/docs/setup/additional-setup/customize-installation-helm/>高级 Helm chart 自定义</a></li><li role=none><a role=treeitem title="安装并使用 Istio CNI 插件，可以让运维人员用更低的权限来部署服务。" href=/v1.16/zh/docs/setup/additional-setup/cni/>安装 Istio CNI 插件</a></li></ul></li></ul></li><li role=treeitem aria-label=任务><a class=main title="如何用 Istio 实现单个特定的目标行为。" href=/v1.16/zh/docs/tasks/>任务</a><ul role=group aria-expanded=true><li role=treeitem aria-label=流量管理><button aria-hidden=true tabindex=-1></button><a title="演示 Istio 的流量路由功能的任务。" href=/v1.16/zh/docs/tasks/traffic-management/>流量管理</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title=如何将请求动态路由到微服务的多个版本。 href=/v1.16/zh/docs/tasks/traffic-management/request-routing/>配置请求路由</a></li><li role=none><a role=treeitem title=此任务说明如何注入故障并测试应用程序的弹性。 href=/v1.16/zh/docs/tasks/traffic-management/fault-injection/>故障注入</a></li><li role=none><a role=treeitem title=展示如何将流量从旧版本迁移到新版本的服务。 href=/v1.16/zh/docs/tasks/traffic-management/traffic-shifting/>流量转移</a></li><li role=none><a role=treeitem title="展示如何将一个服务的 TCP 流量从旧版本迁移到新版本。" href=/v1.16/zh/docs/tasks/traffic-management/tcp-traffic-shifting/>TCP 流量转移</a></li><li role=none><a role=treeitem title="本任务用于示范如何使用 Istio 在 Envoy 中设置请求超时。" href=/v1.16/zh/docs/tasks/traffic-management/request-timeouts/>设置请求超时</a></li><li role=none><a role=treeitem title=本任务展示如何为连接、请求以及异常检测配置熔断。 href=/v1.16/zh/docs/tasks/traffic-management/circuit-breaking/>熔断</a></li><li role=none><a role=treeitem title="此任务演示了 Istio 的流量镜像/影子功能。" href=/v1.16/zh/docs/tasks/traffic-management/mirroring/>镜像</a></li><li role=treeitem aria-label=地域负载均衡><button aria-hidden=true tabindex=-1></button><a title="本系列任务演示如何在 Istio 中配置地域负载均衡。" href=/v1.16/zh/docs/tasks/traffic-management/locality-load-balancing/>地域负载均衡</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title=配置地域负载均衡前的初始化步骤。 href=/v1.16/zh/docs/tasks/traffic-management/locality-load-balancing/before-you-begin/>开始之前</a></li><li role=none><a role=treeitem title=本任务演示如何为网格配置地域故障转移。 href=/v1.16/zh/docs/tasks/traffic-management/locality-load-balancing/failover/>地域故障转移</a></li><li role=none><a role=treeitem title=本指南演示如何配置地域权重分配。 href=/v1.16/zh/docs/tasks/traffic-management/locality-load-balancing/distribute/>地域权重分布</a></li><li role=none><a role=treeitem title=地域负载均衡的清理步骤。 href=/v1.16/zh/docs/tasks/traffic-management/locality-load-balancing/cleanup/>清理</a></li></ul></li><li role=treeitem aria-label=Ingress><button aria-hidden=true tabindex=-1></button><a title="控制 Istio 服务网格的入口流量。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/>Ingress</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述如何配置 Istio Gateway 对象，以将服务暴露至服务网格之外。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/ingress-control/>入口网关</a></li><li role=none><a role=treeitem title="通过 TLS 或 mTLS 将服务暴露到服务网格外。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/secure-ingress/>安全网关</a></li><li role=none><a role=treeitem title="描述了如何在不使用 Ingress Gateway 的情况下，在一个 Sidecar 上终止 TLS 流量。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/ingress-sidecar-tls-termination/>Ingress Sidecar TLS 终止</a></li><li role=none><a role=treeitem title="如何为一个 Ingress Gateway 配置 SNI 透传。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/ingress-sni-passthrough/>无 TLS 终止的 Ingress Gateway</a></li><li role=none><a role=treeitem title="展示如何配置 Kubernetes Ingress 对象，使得从服务网格外部可以访问网格内服务。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/kubernetes-ingress/>Kubernetes Ingress</a></li><li role=none><a role=treeitem title="描述在 Istio 中如何配置 Kubernetes Gateway API。" href=/v1.16/zh/docs/tasks/traffic-management/ingress/gateway-api/>Kubernetes Gateway API</a></li></ul></li><li role=treeitem aria-label=Egress><button aria-hidden=true tabindex=-1></button><a title="控制 Istio 服务网格的出口流量。" href=/v1.16/zh/docs/tasks/traffic-management/egress/>Egress</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述如何配置 Istio 以将流量从网格中的服务路由到外部服务。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-control/>访问外部服务</a></li><li role=none><a role=treeitem title="描述如何配置 Istio 对来自外部服务的流量执行 TLS 发起。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-tls-origination/>Egress TLS Origination</a></li><li role=none><a role=treeitem title="描述如何配置 Istio 通过专用网关服务将流量定向到外部服务。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-gateway/>出口网关</a></li><li role=none><a role=treeitem title="描述了如何配置 Egress 网关，使用 Secret Discovery Service 执行 TLS 链接外部服务。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-gateway-tls-origination-sds/>Egress 网关 TLS 连接 发起的过程 (SDS)</a></li><li role=none><a role=treeitem title="描述如何配置一个 Egress 网关，来向外部服务发起 TLS 连接。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-gateway-tls-origination/>Egress 网关的 TLS 发起过程</a></li><li role=none><a role=treeitem title="描述如何开启通用域中一组主机的 egress，无需单独配置每一台主机。" href=/v1.16/zh/docs/tasks/traffic-management/egress/wildcard-egress-hosts/>Wildcard 主机的 egress</a></li><li role=none><a role=treeitem title="描述如何在 TLS Egress 上配置 SNI 监控和策略。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress_sni_monitoring_and_policies/>TLS Egress 监控和策略配置</a></li><li role=none><a role=treeitem title="展示如何配置 Istio Kubernetes 外部服务。" href=/v1.16/zh/docs/tasks/traffic-management/egress/egress-kubernetes-services/>Kubernetes Egress 流量服务</a></li><li role=none><a role=treeitem title="描述如何配置 Istio 以允许应用程序使用外部 HTTPS 代理。" href=/v1.16/zh/docs/tasks/traffic-management/egress/http-proxy/>使用外部 HTTPS 代理</a></li></ul></li></ul></li><li role=treeitem aria-label=安全><button aria-hidden=true tabindex=-1></button><a title=演示如何保护网格。 href=/v1.16/zh/docs/tasks/security/>安全</a><ul role=group aria-expanded=false><li role=treeitem aria-label=认证><button aria-hidden=true tabindex=-1></button><a title="管控网格服务间的双向 TLS 和终端用户的身份认证。" href=/v1.16/zh/docs/tasks/security/authentication/>认证</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="演示如何使用基于 JWT 声明路由请求的 Istio 身份验证策略。 (Experimental)" href=/v1.16/zh/docs/tasks/security/authentication/jwt-route/>基于 JWT 声明的路由 *</a></li><li role=none><a role=treeitem title="向您展示如何通过使用 Istio 认证策略来设置双向 TLS 和基本的终端用户认证。" href=/v1.16/zh/docs/tasks/security/authentication/authn-policy/>认证策略</a></li><li role=none><a role=treeitem title="阐述如何将 Istio 服务逐步迁移至双向 TLS 通信模式。" href=/v1.16/zh/docs/tasks/security/authentication/mtls-migration/>双向 TLS 迁移</a></li></ul></li><li role=treeitem aria-label=证书管理><button aria-hidden=true tabindex=-1></button><a title="管理 Istio 的证书。" href=/v1.16/zh/docs/tasks/security/cert-management/>证书管理</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="系统管理员如何通过根证书、签名证书和密钥来配置 Istio 的 CA。" href=/v1.16/zh/docs/tasks/security/cert-management/plugin-ca-cert/>插入 CA 证书</a></li><li role=none><a role=treeitem title="如何在 Istiod 中配置和管理 DNS 证书。" href=/v1.16/zh/docs/tasks/security/cert-management/dns-cert/>Istio 的 DNS 证书管理</a></li><li role=none><a role=treeitem title="演示如何使用自定义证书颁发机构（与 Kubernetes CSR API 集成）来提供 Istio 工作负载证书。 (Experimental)" href=/v1.16/zh/docs/tasks/security/cert-management/custom-ca-k8s/>使用 Kubernetes CSR 自定义 CA 集成 *</a></li></ul></li><li role=treeitem aria-label=授权><button aria-hidden=true tabindex=-1></button><a title="展示如何控制到 Istio 服务的访问。" href=/v1.16/zh/docs/tasks/security/authorization/>授权</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="展示如何设置 HTTP 流量访问控制。" href=/v1.16/zh/docs/tasks/security/authorization/authz-http/>HTTP 流量</a></li><li role=none><a role=treeitem title="展示如何设置 TCP 流量的访问控制。" href=/v1.16/zh/docs/tasks/security/authorization/authz-tcp/>TCP 流量</a></li><li role=none><a role=treeitem title="演示如何为 JWT 令牌设置访问控制。" href=/v1.16/zh/docs/tasks/security/authorization/authz-jwt/>JWT 令牌</a></li><li role=none><a role=treeitem title=如何集成访问控制并将其委托给外部授权系统。 href=/v1.16/zh/docs/tasks/security/authorization/authz-custom/>外部授权</a></li><li role=none><a role=treeitem title=如何设置访问控制以明确地拒绝流量。 href=/v1.16/zh/docs/tasks/security/authorization/authz-deny/>明确拒绝</a></li><li role=none><a role=treeitem title=展示如何在入口网关上设置访问控制。 href=/v1.16/zh/docs/tasks/security/authorization/authz-ingress/>入口网关</a></li><li role=none><a role=treeitem title=阐述如何在不更改授权策略的前提下从一个信任域迁移到另一个。 href=/v1.16/zh/docs/tasks/security/authorization/authz-td-migration/>信任域迁移</a></li></ul></li><li role=treeitem aria-label="TLS 配置"><button aria-hidden=true tabindex=-1></button><a title="在 Istio 中配置 TLS。" href=/v1.16/zh/docs/tasks/security/tls-configuration/>TLS 配置</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="演示如何为 Istio 工作负载配置最低版本的 TLS。" href=/v1.16/zh/docs/tasks/security/tls-configuration/workload-min-tls-version/>Istio 工作负载的最低 TLS 版本配置</a></li></ul></li></ul></li><li role=treeitem aria-label=策略执行><button aria-hidden=true tabindex=-1></button><a title=演示策略执行特性。 href=/v1.16/zh/docs/tasks/policy-enforcement/>策略执行</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="此任务将展示如何配置 Istio 来动态地限制服务的流量。" href=/v1.16/zh/docs/tasks/policy-enforcement/rate-limit/>使用 Envoy 启用速率限制</a></li></ul></li><li role=treeitem aria-label=可观察性><button aria-hidden=true tabindex=-1></button><a title=演示如何从网格收集遥测信息。 href=/v1.16/zh/docs/tasks/observability/>可观察性</a><ul role=group aria-expanded=false><li role=treeitem aria-label=指标><button aria-hidden=true tabindex=-1></button><a title="演示 Istio 中指标的收集和查询。" href=/v1.16/zh/docs/tasks/observability/metrics/>指标</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="本任务展示了如何配置 Istio 进行 TCP 服务的指标收集。" href=/v1.16/zh/docs/tasks/observability/metrics/tcp-metrics/>收集 TCP 服务指标</a></li><li role=none><a role=treeitem title="此任务向您展示如何自定义 Istio 指标。" href=/v1.16/zh/docs/tasks/observability/metrics/customize-metrics/>自定义 Istio 指标</a></li><li role=none><a role=treeitem title=此任务向您展示如何通过按类型对请求和响应进行分组来改进遥测。 href=/v1.16/zh/docs/tasks/observability/metrics/classify-metrics/>根据请求或响应对指标进行分类</a></li><li role=none><a role=treeitem title="本任务介绍如何通过 Prometheus 查询 Istio 度量指标。" href=/v1.16/zh/docs/tasks/observability/metrics/querying-metrics/>通过 Prometheus 查询度量指标</a></li><li role=none><a role=treeitem title="此任务展示了如何设置和使用 Istio Dashboard 监控网格流量。" href=/v1.16/zh/docs/tasks/observability/metrics/using-istio-dashboard/>使用 Grafana 可视化指标</a></li></ul></li><li role=treeitem aria-label=日志><button aria-hidden=true tabindex=-1></button><a title="演示 Istio 网格日志的配置、收集和处理。" href=/v1.16/zh/docs/tasks/observability/logs/>日志</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="此任务向您展示如何配置 Envoy 代理将访问日志打印到其标准输出。" href=/v1.16/zh/docs/tasks/observability/logs/access-log/>获取 Envoy 访问日志</a></li></ul></li><li role=treeitem aria-label=分布式追踪><button aria-hidden=true tabindex=-1></button><a title="该任务展示了如何为启用了 Istio 支持的应用进行追踪。" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/>分布式追踪</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Istio 分布式追踪的概述。" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/overview/>概述</a></li><li role=none><a role=treeitem title="了解如何配置代理以向 Jaeger 发送追踪请求。" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/jaeger/>Jaeger</a></li><li role=none><a role=treeitem title="了解如何通过配置代理以向 Zipkin 发送追踪请求。" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/zipkin/>Zipkin</a></li><li role=none><a role=treeitem title="怎样配置代理才能把追踪请求发送到 LightStep。" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/lightstep/>LightStep</a></li><li role=none><a role=treeitem title="如何使用 MeshConfig 和 Pod 注释配置跟踪选项。 (Beta/Experimental)" href=/v1.16/zh/docs/tasks/observability/distributed-tracing/mesh-and-proxy-config/>使用 MeshConfig 和 Pod 注释配置跟踪 *</a></li></ul></li><li role=none><a role=treeitem title="此任务向您展示如何在 Istio 网格中可视化服务。" href=/v1.16/zh/docs/tasks/observability/kiali/>网格可视化</a></li><li role=none><a role=treeitem title="此任务向您展示如何配置从外部访问 Istio 遥测插件。" href=/v1.16/zh/docs/tasks/observability/gateways/>远程访问遥测插件</a></li></ul></li><li role=treeitem aria-label=可扩展性><button aria-hidden=true tabindex=-1></button><a title=演示如何扩展网格行为。 href=/v1.16/zh/docs/tasks/extensibility/>可扩展性</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述如何在网格中使用远程 WebAssembly 模块。 (Alpha)" href=/v1.16/zh/docs/tasks/extensibility/wasm-module-distribution/>WebAssembly 模块分发 *</a></li></ul></li></ul></li><li role=treeitem aria-label=示例><a class=main title="这里包括多个可供 Istio 使用的可完整工作的示例，你可以用来亲自部署和体验这些示例。" href=/v1.16/zh/docs/examples/>示例</a><ul role=group aria-expanded=true><li role=none><a role=treeitem title="部署一个用于演示多种 Istio 特性的应用，由四个单独的微服务构成。" href=/v1.16/zh/docs/examples/bookinfo/>Bookinfo 应用</a></li><li role=none><a role=treeitem title="使用在网格内的虚拟机上运行的 MySQL 服务运行 Bookinfo 应用程序。" href=/v1.16/zh/docs/examples/virtual-machines/>在虚拟机上部署 Bookinfo 应用程序</a></li><li role=treeitem aria-label="使用 Kubernetes 和 Istio 学习微服务"><button aria-hidden=true tabindex=-1></button><a title="该模块化教程为新用户提供了一步步将 Istio 应用于常见微服务场景的动手经验。" href=/v1.16/zh/docs/examples/microservices-istio/>使用 Kubernetes 和 Istio 学习微服务</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/prereq/>前提条件</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/setup-kubernetes-cluster/>设置 Kubernetes 集群</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/setup-local-computer/>设置本地计算机</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/single/>本地运行微服务</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/package-service/>在 Docker 中运行 ratings 服务</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/bookinfo-kubernetes/>使用 Kubernetes 运行 Bookinfo</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/production-testing/>生产测试</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/add-new-microservice-version/>添加一个新版本的 reviews</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/add-istio/>在 productpage 启用 Istio</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/enable-istio-all-microservices/>在所有微服务中启用 Istio</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/istio-ingress-gateway/>配置 Istio Ingress Gateway</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/examples/microservices-istio/logs-istio/>监控 Istio</a></li></ul></li></ul></li><li role=treeitem aria-label=运维><a class=main title="关于部署和管理 Istio 网格的概念、工具和技术。" href=/v1.16/zh/docs/ops/>运维</a><ul role=group aria-expanded=true><li role=treeitem aria-label=部署><button aria-hidden=true tabindex=-1></button><a title="设置 Istio 部署的要求、概念和注意事项。" href=/v1.16/zh/docs/ops/deployment/>部署</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述 Istio 的整体架构与设计目标。" href=/v1.16/zh/docs/ops/deployment/architecture/>架构</a></li><li role=none><a role=treeitem title="描述 Istio 部署中的选择和建议。" href=/v1.16/zh/docs/ops/deployment/deployment-models/>部署模型</a></li><li role=none><a role=treeitem title="介绍 Istio 的性能和可扩展性。" href=/v1.16/zh/docs/ops/deployment/performance-and-scalability/>性能和可扩展性</a></li><li role=none><a role=treeitem title="部署在支持 Istio 的集群中的应用程序的要求。" href=/v1.16/zh/docs/ops/deployment/requirements/>应用程序要求</a></li></ul></li><li role=treeitem aria-label=配置><button aria-hidden=true tabindex=-1></button><a title="配置运行中的 Istio 网格的高级概念和功能。" href=/v1.16/zh/docs/ops/configuration/>配置</a><ul role=group aria-expanded=false><li role=treeitem aria-label=网格配置><button aria-hidden=true tabindex=-1></button><a title=帮助您管理全局网格配置。 href=/v1.16/zh/docs/ops/configuration/mesh/>网格配置</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="简要描述 Istio 对 Kubernetes webhook 的使用以及可能出现的相关问题。" href=/v1.16/zh/docs/ops/configuration/mesh/webhook/>动态准入 Webhook 概述</a></li><li role=none><a role=treeitem title=如何等待资源达到给定的就绪状态。 href=/v1.16/zh/docs/ops/configuration/mesh/config-resource-ready/>等待应用的配置资源状态就绪</a></li><li role=none><a role=treeitem title="为您展示如何对 Istio 服务做健康检查。" href=/v1.16/zh/docs/ops/configuration/mesh/app-health-check/>Istio 服务的健康检查</a></li></ul></li><li role=treeitem aria-label=流量管理><button aria-hidden=true tabindex=-1></button><a title=帮助您管理正在运行的网格的网络方面。 href=/v1.16/zh/docs/ops/configuration/traffic-management/>流量管理</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title=关于如何声明协议。 href=/v1.16/zh/docs/ops/configuration/traffic-management/protocol-selection/>协议选择</a></li><li role=none><a role=treeitem title=有关如何启用和理解地域负载平衡。 href=/v1.16/zh/docs/ops/configuration/traffic-management/locality-load-balancing/>地域负载均衡</a></li><li role=none><a role=treeitem title="如何使用 TLS 配置设置安全的网络流量。" href=/v1.16/zh/docs/ops/configuration/traffic-management/tls-configuration/>TLS 配置</a></li><li role=none><a role=treeitem title="理解 Istio 如何与 DNS 交互。" href=/v1.16/zh/docs/ops/configuration/traffic-management/dns/>DNS</a></li><li role=none><a role=treeitem title="如何配置 DNS 代理。" href=/v1.16/zh/docs/ops/configuration/traffic-management/dns-proxy/>DNS 代理</a></li><li role=none><a role=treeitem title="如何配置 Gateway 网络拓扑。 (Alpha)" href=/v1.16/zh/docs/ops/configuration/traffic-management/network-topologies/>配置 Gateway 网络拓扑 *</a></li><li role=none><a role=treeitem title=如何配置流量在网格集群之间如何分发的。 href=/v1.16/zh/docs/ops/configuration/traffic-management/multicluster/>多集群流量管理</a></li></ul></li><li role=treeitem aria-label=安全><button aria-hidden=true tabindex=-1></button><a title=帮助您管理正在运行的网格的安全性方面。 href=/v1.16/zh/docs/ops/configuration/security/>安全</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="展示使用 Istio 安全策略的通用示例。" href=/v1.16/zh/docs/ops/configuration/security/security-policy-examples/>安全策略示例</a></li><li role=none><a role=treeitem title="使用加固的容器镜像来减小 Istio 的攻击面。" href=/v1.16/zh/docs/ops/configuration/security/harden-docker-images/>加固 Docker 容器镜像</a></li></ul></li><li role=treeitem aria-label=可观测性><button aria-hidden=true tabindex=-1></button><a title=帮助您管理正在运行的网格中的遥测收集和可视化。 href=/v1.16/zh/docs/ops/configuration/telemetry/>可观测性</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="精细化控制 Envoy 的统计信息。" href=/v1.16/zh/docs/ops/configuration/telemetry/envoy-stats/>Envoy 的统计信息</a></li><li role=none><a role=treeitem title="配置 Prometheus 监控 Istio 多集群。" href=/v1.16/zh/docs/ops/configuration/telemetry/monitoring-multicluster-prometheus/>使用 Prometheus 监控 Istio 多集群</a></li></ul></li><li role=treeitem aria-label=可扩展性><button aria-hidden=true tabindex=-1></button><a title=帮助您管理服务网格的扩展。 href=/v1.16/zh/docs/ops/configuration/extensibility/>可扩展性</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="描述 Istio 如何决定是拉取 Wasm 模块还是使用缓存的版本。 (Alpha)" href=/v1.16/zh/docs/ops/configuration/extensibility/wasm-pull-policy/>WebAssembly 模块的拉取策略 *</a></li></ul></li></ul></li><li role=treeitem aria-label=最佳实践><button aria-hidden=true tabindex=-1></button><a title="设置和管理 Istio 服务网格的最佳实践。" href=/v1.16/zh/docs/ops/best-practices/>最佳实践</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="设置 Istio 服务网格时的最佳实践。" href=/v1.16/zh/docs/ops/best-practices/deployment/>Deployment 最佳实践</a></li><li role=none><a role=treeitem title=避免网络或流量管理问题的配置最佳实践。 href=/v1.16/zh/docs/ops/best-practices/traffic-management/>流量管理最佳实践</a></li><li role=none><a role=treeitem title="使用 Istio 保护应用的最佳实践。" href=/v1.16/zh/docs/ops/best-practices/security/>安全最佳实践</a></li><li role=none><a role=treeitem title="描述如何使用镜像签名来验证 Istio 镜像的出处。" href=/v1.16/zh/docs/ops/best-practices/image-signing-validation/>镜像签名和验证</a></li><li role=none><a role=treeitem title="使用 Istio 观测应用时的最佳实践。" href=/v1.16/zh/docs/ops/best-practices/observability/>可观察性最佳实践</a></li></ul></li><li role=treeitem aria-label=常见问题><button aria-hidden=true tabindex=-1></button><a title="描述如何辨认和解决 Istio 中的常见问题。" href=/v1.16/zh/docs/ops/common-problems/>常见问题</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="定位常见的 Istio 流量管理和网络问题的技术。" href=/v1.16/zh/docs/ops/common-problems/network-issues/>流量管理问题</a></li><li role=none><a role=treeitem title="定位常见 Istio 认证、授权、安全相关问题的技巧。" href=/v1.16/zh/docs/ops/common-problems/security-issues/>安全问题</a></li><li role=none><a role=treeitem title="处理 Telemetry 收集问题。" href=/v1.16/zh/docs/ops/common-problems/observability-issues/>可观测性问题</a></li><li role=none><a role=treeitem title="解决 Istio 使用 Kubernetes Webhooks 进行 Sidecar 自动注入的常见问题。" href=/v1.16/zh/docs/ops/common-problems/injection/>Sidecar 自动注入问题</a></li><li role=none><a role=treeitem title=如何解决配置验证的问题。 href=/v1.16/zh/docs/ops/common-problems/validation/>配置验证的问题</a></li></ul></li><li role=treeitem aria-label=诊断工具><button aria-hidden=true tabindex=-1></button><a title="帮助解决 Istio 网格问题的工具和技术。" href=/v1.16/zh/docs/ops/diagnostic-tools/>诊断工具</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Istio 自带的一个可以为服务网格部署提供调试和诊断的补充工具。" href=/v1.16/zh/docs/ops/diagnostic-tools/istioctl/>使用 Istioctl 命令行工具</a></li><li role=none><a role=treeitem title="描述诊断与流量管理相关的 Envoy 配置问题的工具和技术。" href=/v1.16/zh/docs/ops/diagnostic-tools/proxy-cmd/>调试 Envoy 和 Istiod</a></li><li role=none><a role=treeitem title="向您展示如何使用 istioctl describe 来验证您的网格中的 pod 的配置。" href=/v1.16/zh/docs/ops/diagnostic-tools/istioctl-describe/>通过 Istioctl Describe 理解您的网格</a></li><li role=none><a role=treeitem title="演示如何使用 istioctl analyze 来识别配置中的潜在问题。" href=/v1.16/zh/docs/ops/diagnostic-tools/istioctl-analyze/>使用 Istioctl Analyze 诊断配置</a></li><li role=none><a role=treeitem title="介绍如何使用 ControlZ 深入了解正在运行的 istiod 组件。" href=/v1.16/zh/docs/ops/diagnostic-tools/controlz/>组件自检</a></li><li role=none><a role=treeitem title=如何使用组件级别日志来深入了解正在运行的组件的行为。 href=/v1.16/zh/docs/ops/diagnostic-tools/component-logging/>组件日志记录</a></li><li role=none><a role=treeitem title=介绍关于虚拟机调试的技术和工具。 href=/v1.16/zh/docs/ops/diagnostic-tools/virtual-machines/>虚拟机调试</a></li><li role=none><a role=treeitem title=介绍用来诊断多集群和多网络下安装问题的工具和技术。 href=/v1.16/zh/docs/ops/diagnostic-tools/multicluster/>多集群下的故障排除</a></li></ul></li><li role=treeitem aria-label=集成><button aria-hidden=true tabindex=-1></button><a title="能够与 Istio 集成以提供额外功能的其他软件。" href=/v1.16/zh/docs/ops/integrations/>集成</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="关于如何与 cert-manager 集成的相关说明。" href=/v1.16/zh/docs/ops/integrations/certmanager/>cert-manager</a></li><li role=none><a role=treeitem title="关于如何与 Grafana 集成构建 Istio 仪表盘的相关文档。" href=/v1.16/zh/docs/ops/integrations/grafana/>Grafana</a></li><li role=none><a role=treeitem title="如何与 Jaeger 集成。" href=/v1.16/zh/docs/ops/integrations/jaeger/>Jaeger</a></li><li role=none><a role=treeitem title="有关如何与 Kiali 集成的信息。" href=/v1.16/zh/docs/ops/integrations/kiali/>Kiali</a></li><li role=none><a role=treeitem title="如何集成 Prometheus。" href=/v1.16/zh/docs/ops/integrations/prometheus/>Prometheus</a></li><li role=none><a role=treeitem title="如何与 Zipkin 进行集成。" href=/v1.16/zh/docs/ops/integrations/zipkin/>Zipkin</a></li></ul></li></ul></li><li role=treeitem aria-label=发布><a class=main title="与 Istio 发布有关的信息。" href=/v1.16/zh/docs/releases/>发布</a><ul role=group aria-expanded=true><li role=none><a role=treeitem title=特性及其发布阶段的列表。 href=/v1.16/zh/docs/releases/feature-stages/>功能状态</a></li><li role=none><a role=treeitem title=如果发现错误该怎么办。 href=/v1.16/zh/docs/releases/bugs/>报告错误</a></li><li role=none><a role=treeitem title=我们如何处理安全漏洞。 href=/v1.16/zh/docs/releases/security-vulnerabilities/>安全漏洞</a></li><li role=none><a role=treeitem title="当前支持的 Istio 版本。" href=/v1.16/zh/docs/releases/supported-releases/>版本支持</a></li><li role=treeitem aria-label=贡献文档><button aria-hidden=true tabindex=-1></button><a title="详细介绍了如何创建和维护 Istio 文档。" href=/v1.16/zh/docs/releases/contribute/>贡献文档</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="介绍如何为 Istio 贡献新文档。" href=/v1.16/zh/docs/releases/contribute/add-content/>添加新文档</a></li><li role=none><a role=treeitem title="详细说明如何将已停用的文档提交给 Istio。" href=/v1.16/zh/docs/releases/contribute/remove-content/>删除已停用的文档</a></li><li role=none><a role=treeitem title=介绍如何在本地进行本网站的构建，测试，运行和预览。 href=/v1.16/zh/docs/releases/contribute/build/>本地构建和运行本网站</a></li><li role=none><a role=treeitem title=介绍了文档中使用的文章头及其可用字段。 href=/v1.16/zh/docs/releases/contribute/front-matter/>文章头部</a></li><li role=none><a role=treeitem title="向您展示如何审阅和批准对 Istio 文档和网站的更改。" href=/v1.16/zh/docs/releases/contribute/review/>文档审阅流程</a></li><li role=none><a role=treeitem title=介绍如何在您的文档中添加代码。 href=/v1.16/zh/docs/releases/contribute/code-blocks/>添加代码块</a></li><li role=none><a role=treeitem title="介绍可用的 shortcode 及其用法。" href=/v1.16/zh/docs/releases/contribute/shortcodes/>使用 Shortcode</a></li><li role=none><a role=treeitem title="介绍 Istio 文档的格式标准。" href=/v1.16/zh/docs/releases/contribute/formatting/>格式标准</a></li><li role=none><a role=treeitem title="介绍 Istio 文档所使用的风格规则。" href=/v1.16/zh/docs/releases/contribute/style-guide/>风格指南</a></li><li role=none><a role=treeitem title="解释 Istio 文档中使用的术语标准。" href=/v1.16/zh/docs/releases/contribute/terminology/>术语标准</a></li><li role=none><a role=treeitem title="为 Istio 文档创建图表提供素材和说明。" href=/v1.16/zh/docs/releases/contribute/diagrams/>创建图表指南</a></li><li role=none><a role=treeitem title="向您展示如何使用 GitHub 参与贡献 Istio 文档。" href=/v1.16/zh/docs/releases/contribute/github/>使用 GitHub 参与社区活动</a></li></ul></li><li role=none><a role=treeitem title=该网站的最新更改列表。 href=/v1.16/zh/docs/releases/log/>网站内容更改</a></li></ul></li><li role=treeitem aria-label=参考><a class=main title="参考部分包含详细的权威参考资料，如命令行选项、配置选项和 API 调用参数。" href=/v1.16/zh/docs/reference/>参考</a><ul role=group aria-expanded=true><li role=treeitem aria-label=配置><button aria-hidden=true tabindex=-1></button><a title=关于配置选项的详细信息。 href=/v1.16/zh/docs/reference/config/>配置</a><ul role=group aria-expanded=false><li role=none><a role=treeitem title="Telemetry configuration for workloads." href=/v1.16/zh/docs/reference/config/telemetry/>Telemetry</a></li><li role=none><a role=treeitem title="描述使用 Helm chart 安装 Istio 时的可选项。" href=/v1.16/zh/docs/reference/config/installation-options/>安装选项（Helm）</a></li><li role=none><a role=treeitem title="Describes the structure of messages generated by Istio analyzers." href=/v1.16/zh/docs/reference/config/istio.analysis.v1alpha1/>Analysis Messages</a></li><li role=none><a role=treeitem title="Configuration affecting the service mesh as a whole." href=/v1.16/zh/docs/reference/config/istio.mesh.v1alpha1/>Global Mesh Options</a></li><li role=none><a role=treeitem title="Configuration affecting Istio control plane installation version and shape." href=/v1.16/zh/docs/reference/config/istio.operator.v1alpha1/>IstioOperator Options</a></li><li role=none><a role=treeitem title=描述“状态”字段在配置工作流程中的作用。 href=/v1.16/zh/docs/reference/config/config-status/>状态字段配置</a></li><li role=treeitem aria-label=流量管理><button aria-hidden=true tabindex=-1></button><a title="描述如何配置 HTTP/TCP 路由功能。" href=/v1.16/zh/docs/reference/config/networking/>流量管理</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Configuration affecting load balancing, outlier detection, etc." href=/v1.16/zh/docs/reference/config/networking/destination-rule/>Destination Rule</a></li><li role=none><a role=treeitem title="Customizing Envoy configuration generated by Istio." href=/v1.16/zh/docs/reference/config/networking/envoy-filter/>Envoy Filter</a></li><li role=none><a role=treeitem title="Configuration affecting edge load balancer." href=/v1.16/zh/docs/reference/config/networking/gateway/>Gateway</a></li><li role=none><a role=treeitem title="Provides configuration for individual workloads." href=/v1.16/zh/docs/reference/config/networking/proxy-config/>ProxyConfig</a></li><li role=none><a role=treeitem title="Configuration affecting service registry." href=/v1.16/zh/docs/reference/config/networking/service-entry/>Service Entry</a></li><li role=none><a role=treeitem title="Configuration affecting network reachability of a sidecar." href=/v1.16/zh/docs/reference/config/networking/sidecar/>Sidecar</a></li><li role=none><a role=treeitem title="Configuration affecting label/content routing, sni routing, etc." href=/v1.16/zh/docs/reference/config/networking/virtual-service/>Virtual Service</a></li><li role=none><a role=treeitem title="Configuration affecting VMs onboarded into the mesh." href=/v1.16/zh/docs/reference/config/networking/workload-entry/>Workload Entry</a></li><li role=none><a role=treeitem title="Describes a collection of workload instances." href=/v1.16/zh/docs/reference/config/networking/workload-group/>Workload Group</a></li></ul></li><li role=treeitem aria-label=Security><button aria-hidden=true tabindex=-1></button><a title="如何配置 Istio 的安全功能。" href=/v1.16/zh/docs/reference/config/security/>Security</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Configuration to validate JWT." href=/v1.16/zh/docs/reference/config/security/jwt/>JWTRule</a></li><li role=none><a role=treeitem title="Peer authentication configuration for workloads." href=/v1.16/zh/docs/reference/config/security/peer_authentication/>PeerAuthentication</a></li><li role=none><a role=treeitem title="Request authentication configuration for workloads." href=/v1.16/zh/docs/reference/config/security/request_authentication/>RequestAuthentication</a></li><li role=none><a role=treeitem title="Configuration for access control on workloads." href=/v1.16/zh/docs/reference/config/security/authorization-policy/>Authorization Policy</a></li><li role=none><a role=treeitem title=授权策略中支持的条件。 href=/v1.16/zh/docs/reference/config/security/conditions/>授权策略</a></li><li role=none><a role=treeitem title=受支持的约束条件和属性。 href=/v1.16/zh/docs/reference/config/security/constraints-and-properties/>RBAC 约束和属性（不建议使用）</a></li></ul></li><li role=none><a role=treeitem title="通过 Istio 遥测导出的 Istio 标准指标。" href=/v1.16/zh/docs/reference/config/metrics/>Istio 标准指标</a></li><li role=treeitem aria-label=常见类型><button aria-hidden=true tabindex=-1></button><a title="描述 Istio API 中的常见类型。" href=/v1.16/zh/docs/reference/config/type/>常见类型</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title="Definition of a workload selector." href=/v1.16/zh/docs/reference/config/type/workload-selector/>Workload Selector</a></li></ul></li><li role=none><a role=treeitem title="Resource annotations used by Istio." href=/v1.16/zh/docs/reference/config/annotations/>Resource Annotations</a></li><li role=none><a role=treeitem title="Resource labels used by Istio." href=/v1.16/zh/docs/reference/config/labels/>Resource Labels</a></li><li role=treeitem aria-label=配置分析消息><button aria-hidden=true tabindex=-1></button><a title=记录配置分析期间产生的各个错误和警告消息。 href=/v1.16/zh/docs/reference/config/analysis/>配置分析消息</a><ul role=group aria-expanded=false class=leaf-section><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0136/>AlphaAnnotation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/message-format/>Analyzer Message Format</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0109/>ConflictingMeshGatewayVirtualServiceHosts</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0110/>ConflictingSidecarWorkloadSelectors</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0116/>DeploymentAssociatedToMultipleServices</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0137/>DeploymentConflictingPorts</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0117/>DeploymentRequiresServiceAssociated</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0002/>Deprecated</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0135/>DeprecatedAnnotation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0153/>EnvoyFilterUsesAddOperationIncorrectly</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0151/>EnvoyFilterUsesRelativeOperation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0155/>EnvoyFilterUsesRelativeOperationWithProxyVersion</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0154/>EnvoyFilterUsesRemoveOperationIncorrectly</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0152/>EnvoyFilterUsesReplaceOperationIncorrectly</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0150/>ExternalNameServiceTypeInvalidPortName</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0104/>GatewayPortNotOnWorkload</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0001/>InternalError</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0125/>InvalidAnnotation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0144/>InvalidApplicationUID</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0122/>InvalidRegexp</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0105/>IstioProxyImageMismatch</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0119/>JwtFailureDueToInvalidServicePortPrefix</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0107/>MisplacedAnnotation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0113/>MTLSPolicyConflict</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0111/>MultipleSidecarsWithoutWorkloadSelectors</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0123/>NamespaceMultipleInjectionLabels</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0102/>NamespaceNotInjected</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0127/>NoMatchingWorkloadsFound</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0128/>NoServerCertificateVerificationDestinationLevel</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0129/>NoServerCertificateVerificationPortLevel</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0103/>PodMissingProxy</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0118/>PortNameIsNotUnderNamingConvention</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0101/>ReferencedResourceNotFound</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0106/>SchemaValidationError</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0108/>UnknownAnnotation</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0112/>VirtualServiceDestinationPortSelectorRequired</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0132/>VirtualServiceHostNotFoundInGateway</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0131/>VirtualServiceIneffectiveMatch</a></li><li role=none><a role=treeitem title href=/v1.16/zh/docs/reference/config/analysis/ist0130/>VirtualServiceUnreachableRule</a></li></ul></li></ul></li><li role=treeitem aria-label=命令><button class=show aria-hidden=true tabindex=-1></button><a title="描述 Istio 命令和工具的用法及选项。" href=/v1.16/zh/docs/reference/commands/>命令</a><ul role=group aria-expanded=true class=leaf-section><li role=none><a role=treeitem title="Install and configure Istio CNI plugin on a node, detect and repair pod which is broken by race condition." href=/v1.16/zh/docs/reference/commands/install-cni/>install-cni</a></li><li role=none><a role=treeitem title="Istio control interface." href=/v1.16/zh/docs/reference/commands/istioctl/>istioctl</a></li><li role=none><a role=treeitem title="The Istio operator." href=/v1.16/zh/docs/reference/commands/operator/>operator</a></li><li role=none><a role=treeitem title="Istio Pilot agent." href=/v1.16/zh/docs/reference/commands/pilot-agent/>pilot-agent</a></li><li role=none><a role=treeitem title="Istio Pilot." href=/v1.16/zh/docs/reference/commands/pilot-discovery/>pilot-discovery</a></li></ul></li><li role=none><a role=treeitem title="Istio 常用术语的词汇表。" href=/v1.16/zh/docs/reference/glossary/>术语表</a></li></ul></li></ul></div></div></div></nav></div><div class=article-container><button id=sidebar-toggle class=main-navigation-toggle aria-label="Open sidebar"><svg class="icon hamburger-sidebar"><use xlink:href="/v1.16/img/icons.svg#hamburger-sidebar"/></svg>
目录</button><article aria-labelledby=title><nav aria-label=Breadcrumb><ol><li><a href=/v1.16/zh/docs/ title="了解如何部署、使用和运维 Istio。">文档</a><svg class="icon breadcrumb-arrow"><use xlink:href="/v1.16/img/icons.svg#breadcrumb-arrow"/></svg></li><li><a href=/v1.16/zh/docs/reference/ title="参考部分包含详细的权威参考资料，如命令行选项、配置选项和 API 调用参数。">参考</a><svg class="icon breadcrumb-arrow"><use xlink:href="/v1.16/img/icons.svg#breadcrumb-arrow"/></svg></li><li><a href=/v1.16/zh/docs/reference/commands/ title="描述 Istio 命令和工具的用法及选项。">命令</a><svg class="icon breadcrumb-arrow"><use xlink:href="/v1.16/img/icons.svg#breadcrumb-arrow"/></svg></li><li>istioctl</li></ol></nav><div class=title-area><div style=width:100%><h1 id=title>istioctl</h1><p class=byline><span class=reading-time title="22117 字"><svg class="icon clock"><use xlink:href="/v1.16/img/icons.svg#clock"/></svg><span>&nbsp;</span>阅读大约需要 104 分钟</span>
<span>&nbsp;</span>
<span></span></p></div></div><nav class=toc-inlined aria-label="Table of Contents"><div><hr><ol><li role=none aria-label="istioctl admin"><a href=#istioctl-admin>admin</a><li role=none aria-label="istioctl admin log"><a href=#istioctl-admin-log>admin log</a><li role=none aria-label="istioctl analyze"><a href=#istioctl-analyze>analyze</a><li role=none aria-label="istioctl authz"><a href=#istioctl-authz>authz</a><li role=none aria-label="istioctl bug-report"><a href=#istioctl-bug-report>bug-report</a><li role=none aria-label="istioctl bug-report version"><a href=#istioctl-bug-report-version>bug-report version</a><li role=none aria-label="istioctl completion"><a href=#istioctl-completion>completion</a><li role=none aria-label="istioctl completion bash"><a href=#istioctl-completion-bash>completion bash</a><li role=none aria-label="istioctl completion fish"><a href=#istioctl-completion-fish>completion fish</a><li role=none aria-label="istioctl completion powershell"><a href=#istioctl-completion-powershell>completion powershell</a><li role=none aria-label="istioctl completion zsh"><a href=#istioctl-completion-zsh>completion zsh</a><li role=none aria-label="istioctl dashboard"><a href=#istioctl-dashboard>dashboard</a><li role=none aria-label="istioctl dashboard controlz"><a href=#istioctl-dashboard-controlz>dashboard controlz</a><li role=none aria-label="istioctl dashboard envoy"><a href=#istioctl-dashboard-envoy>dashboard envoy</a><li role=none aria-label="istioctl dashboard grafana"><a href=#istioctl-dashboard-grafana>dashboard grafana</a><li role=none aria-label="istioctl dashboard jaeger"><a href=#istioctl-dashboard-jaeger>dashboard jaeger</a><li role=none aria-label="istioctl dashboard kiali"><a href=#istioctl-dashboard-kiali>dashboard kiali</a><li role=none aria-label="istioctl dashboard prometheus"><a href=#istioctl-dashboard-prometheus>dashboard prometheus</a><li role=none aria-label="istioctl dashboard skywalking"><a href=#istioctl-dashboard-skywalking>dashboard skywalking</a><li role=none aria-label="istioctl dashboard zipkin"><a href=#istioctl-dashboard-zipkin>dashboard zipkin</a><li role=none aria-label="istioctl experimental"><a href=#istioctl-experimental>experimental</a><li role=none aria-label="istioctl experimental add-to-mesh"><a href=#istioctl-experimental-add-to-mesh>experimental add-to-mesh</a><li role=none aria-label="istioctl experimental add-to-mesh deployment"><a href=#istioctl-experimental-add-to-mesh-deployment>experimental add-to-mesh deployment</a><li role=none aria-label="istioctl experimental add-to-mesh external-service"><a href=#istioctl-experimental-add-to-mesh-external-service>experimental add-to-mesh external-service</a><li role=none aria-label="istioctl experimental add-to-mesh service"><a href=#istioctl-experimental-add-to-mesh-service>experimental add-to-mesh service</a><li role=none aria-label="istioctl experimental authz"><a href=#istioctl-experimental-authz>experimental authz</a><li role=none aria-label="istioctl experimental authz check"><a href=#istioctl-experimental-authz-check>experimental authz check</a><li role=none aria-label="istioctl experimental check-inject"><a href=#istioctl-experimental-check-inject>experimental check-inject</a><li role=none aria-label="istioctl experimental config"><a href=#istioctl-experimental-config>experimental config</a><li role=none aria-label="istioctl experimental config list"><a href=#istioctl-experimental-config-list>experimental config list</a><li role=none aria-label="istioctl experimental create-remote-secret"><a href=#istioctl-experimental-create-remote-secret>experimental create-remote-secret</a><li role=none aria-label="istioctl experimental describe"><a href=#istioctl-experimental-describe>experimental describe</a><li role=none aria-label="istioctl experimental describe pod"><a href=#istioctl-experimental-describe-pod>experimental describe pod</a><li role=none aria-label="istioctl experimental describe service"><a href=#istioctl-experimental-describe-service>experimental describe service</a><li role=none aria-label="istioctl experimental envoy-stats"><a href=#istioctl-experimental-envoy-stats>experimental envoy-stats</a><li role=none aria-label="istioctl experimental injector"><a href=#istioctl-experimental-injector>experimental injector</a><li role=none aria-label="istioctl experimental injector list"><a href=#istioctl-experimental-injector-list>experimental injector list</a><li role=none aria-label="istioctl experimental internal-debug"><a href=#istioctl-experimental-internal-debug>experimental internal-debug</a><li role=none aria-label="istioctl experimental kube-uninject"><a href=#istioctl-experimental-kube-uninject>experimental kube-uninject</a><li role=none aria-label="istioctl experimental metrics"><a href=#istioctl-experimental-metrics>experimental metrics</a><li role=none aria-label="istioctl experimental precheck"><a href=#istioctl-experimental-precheck>experimental precheck</a><li role=none aria-label="istioctl experimental proxy-status"><a href=#istioctl-experimental-proxy-status>experimental proxy-status</a><li role=none aria-label="istioctl experimental remote-clusters"><a href=#istioctl-experimental-remote-clusters>experimental remote-clusters</a><li role=none aria-label="istioctl experimental remove-from-mesh"><a href=#istioctl-experimental-remove-from-mesh>experimental remove-from-mesh</a><li role=none aria-label="istioctl experimental remove-from-mesh deployment"><a href=#istioctl-experimental-remove-from-mesh-deployment>experimental remove-from-mesh deployment</a><li role=none aria-label="istioctl experimental remove-from-mesh external-service"><a href=#istioctl-experimental-remove-from-mesh-external-service>experimental remove-from-mesh external-service</a><li role=none aria-label="istioctl experimental remove-from-mesh service"><a href=#istioctl-experimental-remove-from-mesh-service>experimental remove-from-mesh service</a><li role=none aria-label="istioctl experimental revision"><a href=#istioctl-experimental-revision>experimental revision</a><li role=none aria-label="istioctl experimental revision describe"><a href=#istioctl-experimental-revision-describe>experimental revision describe</a><li role=none aria-label="istioctl experimental revision list"><a href=#istioctl-experimental-revision-list>experimental revision list</a><li role=none aria-label="istioctl experimental revision tag"><a href=#istioctl-experimental-revision-tag>experimental revision tag</a><li role=none aria-label="istioctl experimental revision tag generate"><a href=#istioctl-experimental-revision-tag-generate>experimental revision tag generate</a><li role=none aria-label="istioctl experimental revision tag list"><a href=#istioctl-experimental-revision-tag-list>experimental revision tag list</a><li role=none aria-label="istioctl experimental revision tag remove"><a href=#istioctl-experimental-revision-tag-remove>experimental revision tag remove</a><li role=none aria-label="istioctl experimental revision tag set"><a href=#istioctl-experimental-revision-tag-set>experimental revision tag set</a><li role=none aria-label="istioctl experimental uninstall"><a href=#istioctl-experimental-uninstall>experimental uninstall</a><li role=none aria-label="istioctl experimental version"><a href=#istioctl-experimental-version>experimental version</a><li role=none aria-label="istioctl experimental wait"><a href=#istioctl-experimental-wait>experimental wait</a><li role=none aria-label="istioctl experimental workload"><a href=#istioctl-experimental-workload>experimental workload</a><li role=none aria-label="istioctl experimental workload entry"><a href=#istioctl-experimental-workload-entry>experimental workload entry</a><li role=none aria-label="istioctl experimental workload entry configure"><a href=#istioctl-experimental-workload-entry-configure>experimental workload entry configure</a><li role=none aria-label="istioctl experimental workload group"><a href=#istioctl-experimental-workload-group>experimental workload group</a><li role=none aria-label="istioctl experimental workload group create"><a href=#istioctl-experimental-workload-group-create>experimental workload group create</a><li role=none aria-label="istioctl install"><a href=#istioctl-install>install</a><li role=none aria-label="istioctl kube-inject"><a href=#istioctl-kube-inject>kube-inject</a><li role=none aria-label="istioctl manifest"><a href=#istioctl-manifest>manifest</a><li role=none aria-label="istioctl manifest diff"><a href=#istioctl-manifest-diff>manifest diff</a><li role=none aria-label="istioctl manifest generate"><a href=#istioctl-manifest-generate>manifest generate</a><li role=none aria-label="istioctl manifest install"><a href=#istioctl-manifest-install>manifest install</a><li role=none aria-label="istioctl operator"><a href=#istioctl-operator>operator</a><li role=none aria-label="istioctl operator dump"><a href=#istioctl-operator-dump>operator dump</a><li role=none aria-label="istioctl operator init"><a href=#istioctl-operator-init>operator init</a><li role=none aria-label="istioctl operator remove"><a href=#istioctl-operator-remove>operator remove</a><li role=none aria-label="istioctl options"><a href=#istioctl-options>options</a><li role=none aria-label="istioctl profile"><a href=#istioctl-profile>profile</a><li role=none aria-label="istioctl profile diff"><a href=#istioctl-profile-diff>profile diff</a><li role=none aria-label="istioctl profile dump"><a href=#istioctl-profile-dump>profile dump</a><li role=none aria-label="istioctl profile list"><a href=#istioctl-profile-list>profile list</a><li role=none aria-label="istioctl proxy-config"><a href=#istioctl-proxy-config>proxy-config</a><li role=none aria-label="istioctl proxy-config all"><a href=#istioctl-proxy-config-all>proxy-config all</a><li role=none aria-label="istioctl proxy-config bootstrap"><a href=#istioctl-proxy-config-bootstrap>proxy-config bootstrap</a><li role=none aria-label="istioctl proxy-config cluster"><a href=#istioctl-proxy-config-cluster>proxy-config cluster</a><li role=none aria-label="istioctl proxy-config endpoint"><a href=#istioctl-proxy-config-endpoint>proxy-config endpoint</a><li role=none aria-label="istioctl proxy-config listener"><a href=#istioctl-proxy-config-listener>proxy-config listener</a><li role=none aria-label="istioctl proxy-config log"><a href=#istioctl-proxy-config-log>proxy-config log</a><li role=none aria-label="istioctl proxy-config rootca-compare"><a href=#istioctl-proxy-config-rootca-compare>proxy-config rootca-compare</a><li role=none aria-label="istioctl proxy-config route"><a href=#istioctl-proxy-config-route>proxy-config route</a><li role=none aria-label="istioctl proxy-config secret"><a href=#istioctl-proxy-config-secret>proxy-config secret</a><li role=none aria-label="istioctl proxy-status"><a href=#istioctl-proxy-status>proxy-status</a><li role=none aria-label="istioctl tag"><a href=#istioctl-tag>tag</a><li role=none aria-label="istioctl tag generate"><a href=#istioctl-tag-generate>tag generate</a><li role=none aria-label="istioctl tag list"><a href=#istioctl-tag-list>tag list</a><li role=none aria-label="istioctl tag remove"><a href=#istioctl-tag-remove>tag remove</a><li role=none aria-label="istioctl tag set"><a href=#istioctl-tag-set>tag set</a><li role=none aria-label="istioctl uninstall"><a href=#istioctl-uninstall>uninstall</a><li role=none aria-label="istioctl upgrade"><a href=#istioctl-upgrade>upgrade</a><li role=none aria-label="istioctl validate"><a href=#istioctl-validate>validate</a><li role=none aria-label="istioctl verify-install"><a href=#istioctl-verify-install>verify-install</a><li role=none aria-label="istioctl version"><a href=#istioctl-version>version</a><li role=none aria-label="Environment variables"><a href=#envvars>Environment variables</a><li role=none aria-label="Exported metrics"><a href=#metrics>Exported metrics</a></ol><hr></div></nav><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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--selector &lt;string></code></td><td><code>-l</code></td><td>label selector (default `app=istiod`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--ctrlz_port &lt;int></code></td><td></td><td>ControlZ port (default `9876`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--level &lt;string></code></td><td></td><td>Comma-separated list of output logging level for scopes in format &lt;scope>:&lt;level>[,&lt;scope>:&lt;level>,...]Possible values for &lt;level>: none, error, warn, info, debug (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td><code>-l</code></td><td>label selector (default `app=istiod`)</td></tr><tr><td><code>--stack-trace-level &lt;string></code></td><td></td><td>Comma-separated list of stack trace level for scopes in format &lt;scope>:&lt;stack-trace-level>[,&lt;scope>:&lt;stack-trace-level>,...] Possible values for &lt;stack-trace-level>: none, error, warn, info, debug (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 '=false' or set $TERM to dumb</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--failure-threshold &lt;Level></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'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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></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></code></td><td></td><td>Overrides the mesh config values to use for analysis. (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></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>=&lt;resource> (e.g. '--suppress "IST0102=DestinationRule primary-dr.default"'). Can be repeated. You can include the wildcard character '*' to support a partial match (e.g. '--suppress "IST0102=DestinationRule *.default" ). (default `[]`)</td></tr><tr><td><code>--timeout &lt;duration></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 'must be in (ns1 OR ns2) AND (dep1 OR dep2) AND (cntr1 OR cntr2)...'
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 '*' 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 'p' in namespaces beginning with 'n' and having label 'l' with value beginning with 'v'.)</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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--critical-errs &lt;stringSlice></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></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't fetch or write.</td></tr><tr><td><code>--duration &lt;duration></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></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></code></td><td></td><td>Spec for which pod'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></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></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></code></td><td></td><td>Spec for which pod's proxy logs to include in the archive. See above for format and examples. (default `[]`)</td></tr><tr><td><code>--istio-namespace &lt;string></code></td><td></td><td>Namespace where Istio control plane is installed. (default `istio-system`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--rps-limit &lt;int></code></td><td></td><td>Requests per second limit to the Kubernetes API server, defaults to 10.A higher limit can make bug report collection much faster. (default `0`)</td></tr><tr><td><code>--start-time &lt;string></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></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></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></code></td><td></td><td>Name of the kubeconfig Context to use. (default ``)</td></tr><tr><td><code>--critical-errs &lt;stringSlice></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></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't fetch or write.</td></tr><tr><td><code>--duration &lt;duration></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></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></code></td><td></td><td>Spec for which pod'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></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></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></code></td><td></td><td>Spec for which pod's proxy logs to include in the archive. See above for format and examples. (default `[]`)</td></tr><tr><td><code>--istio-namespace &lt;string></code></td><td></td><td>Namespace where Istio control plane is installed. (default `istio-system`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Path to kube config. (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>One of 'yaml' or 'json'. (default ``)</td></tr><tr><td><code>--rps-limit &lt;int></code></td><td></td><td>Requests per second limit to the Kubernetes API server, defaults to 10.A higher limit can make bug report collection much faster. (default `0`)</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></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></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></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'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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 'bash-completion' package.
If it is not installed already, you can install it via your OS'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 > /etc/bash_completion.d/istioctl</p><p>#### macOS:</p><p>istioctl completion bash > $(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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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 > ~/.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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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 "autoload -U compinit; compinit" >> ~/.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 > "${fpath[1]}/_istioctl"</p><p>#### macOS:</p><p>istioctl completion zsh > $(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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--port &lt;int></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--ctrlz_port &lt;int></code></td><td></td><td>ControlZ port (default `9876`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--selector &lt;string></code></td><td><code>-l</code></td><td>Label selector (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--selector &lt;string></code></td><td><code>-l</code></td><td>Label selector (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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'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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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'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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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'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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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'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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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'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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-p</code></td><td>Local port to listen to (default `0`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental add-to-mesh' restarts pods with an Istio sidecar or configures meshed pod access to external services.
Use 'add-to-mesh' as an alternate to namespace-wide auto injection for troubleshooting compatibility.</p><p>The 'remove-from-mesh' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--injectConfigFile &lt;string></code></td><td></td><td>Injection configuration filename. Cannot be used with --injectConfigMapName (default ``)</td></tr><tr><td><code>--injectConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio sidecar injection, key should be "config". (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--meshConfigFile &lt;string></code></td><td></td><td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set (default ``)</td></tr><tr><td><code>--meshConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--valuesFile &lt;string></code></td><td></td><td>Injection values configuration filename. (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental add-to-mesh deployment' restarts pods with the Istio sidecar. Use 'add-to-mesh'
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 'add-to-mesh' you must re-deploy it and troubleshoot it for Istio compatibility.
See https://istio.io/v1.16/docs/ops/deployment/requirements/</p><p>See also 'istioctl experimental remove-from-mesh deployment' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--injectConfigFile &lt;string></code></td><td></td><td>Injection configuration filename. Cannot be used with --injectConfigMapName (default ``)</td></tr><tr><td><code>--injectConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio sidecar injection, key should be "config". (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--meshConfigFile &lt;string></code></td><td></td><td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set (default ``)</td></tr><tr><td><code>--meshConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--valuesFile &lt;string></code></td><td></td><td>Injection values configuration filename. (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 'istioctl experimental remove-from-mesh external-service' 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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--injectConfigFile &lt;string></code></td><td></td><td>Injection configuration filename. Cannot be used with --injectConfigMapName (default ``)</td></tr><tr><td><code>--injectConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio sidecar injection, key should be "config". (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--labels &lt;stringSlice></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></code></td><td></td><td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set (default ``)</td></tr><tr><td><code>--meshConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--serviceaccount &lt;string></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></code></td><td></td><td>Injection values configuration filename. (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 'add-to-mesh'
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 'add-to-mesh' you must re-deploy it and troubleshoot it for Istio compatibility.
See https://istio.io/v1.16/docs/ops/deployment/requirements/</p><p>See also 'istioctl experimental remove-from-mesh service' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--injectConfigFile &lt;string></code></td><td></td><td>Injection configuration filename. Cannot be used with --injectConfigMapName (default ``)</td></tr><tr><td><code>--injectConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio sidecar injection, key should be "config". (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--meshConfigFile &lt;string></code></td><td></td><td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set (default ``)</td></tr><tr><td><code>--meshConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--valuesFile &lt;string></code></td><td></td><td>Injection values configuration filename. (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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-check-inject>istioctl experimental check-inject</h2><p>Checks associated resources of the given resource, and running webhooks to examine whether the pod can be or will be injected or not.</p><pre class=language-bash><code>istioctl experimental check-inject [&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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--labels &lt;string></code></td><td><code>-l</code></td><td>Check namespace and label pairs injection status, split multiple labels by commas (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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-check-inject Examples">Examples</h3><pre class=language-bash><code> # Check the injection status of a pod
istioctl experimental check-inject details-v1-fcff6c49c-kqnfk.test
# Check the injection status of a pod under a deployment
istioctl x check-inject deployment/details-v1
# Check the injection status of a pod under a deployment in namespace test
istioctl x check-inject deployment/details-v1 -n test
# Check the injection status of label pairs in a specific namespace before actual injection
istioctl x check-inject -n test -l app=helloworld,version=v1
</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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></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></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></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't exist.</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--name &lt;string></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's UUID of the local cluster will be used. (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--secret-name &lt;string></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></code></td><td></td><td>The address and port of the Kubernetes API server. (default ``)</td></tr><tr><td><code>--service-account &lt;string></code></td><td></td><td>Create a secret with this service account's credentials. Default value is "istio-reader-service-account" if --type is "remote", "istiod" if --type is "config". (default ``)</td></tr><tr><td><code>--type &lt;SecretType></code></td><td></td><td>Type of the generated secret. supported values = [remote config] (default `remote`)</td></tr><tr><td><code>--vklog &lt;Level></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 create-remote-secret --name c0 \
| kubectl --kubeconfig=c1.yaml apply -f -
# Delete a secret that was previously installed in c1
istioctl --kubeconfig=c0.yaml 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 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td></td><td>XDS Endpoint certificate directory (default ``)</td></tr><tr><td><code>--context &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--timeout &lt;duration></code></td><td></td><td>The duration to wait before failing (default `30s`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>XDS Endpoint (default ``)</td></tr><tr><td><code>--xds-label &lt;string></code></td><td></td><td>Istiod pod label selector (default ``)</td></tr><tr><td><code>--xds-port &lt;int></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 "istioctl kube-inject -f".</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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--filename &lt;string></code></td><td><code>-f</code></td><td>Input Kubernetes resource filename (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>Modified output Kubernetes resource filename (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--duration &lt;duration></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></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></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></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></code></td><td></td><td>XDS Endpoint certificate directory (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--timeout &lt;duration></code></td><td></td><td>The duration to wait before failing (default `30s`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>XDS Endpoint (default ``)</td></tr><tr><td><code>--xds-label &lt;string></code></td><td></td><td>Istiod pod label selector (default ``)</td></tr><tr><td><code>--xds-port &lt;int></code></td><td></td><td>Istiod pod port (default `15012`)</td></tr><tr><td><code>--xds-via-agents</code></td><td></td><td>Access Istiod via the tap service of each agent</td></tr><tr><td><code>--xds-via-agents-limit &lt;xds-via-agent></code></td><td></td><td>Maximum number of pods being visited by istioctl when xds-via-agent flag is true.To iterate all the agent pods without limit, set to 0 (default `100`)</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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental remove-from-mesh' restarts pods without an Istio sidecar or removes external service access configuration.
Use 'remove-from-mesh' to quickly test uninjected behavior as part of compatibility troubleshooting.
The 'add-to-mesh' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental remove-from-mesh deployment' restarts pods with the Istio sidecar un-injected.
'remove-from-mesh' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental remove-from-mesh external-service' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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>'istioctl experimental remove-from-mesh service' restarts pods with the Istio sidecar un-injected.
'remove-from-mesh' 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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 "istio.io/rev=revision-a" to "istio.io/rev=revision-b" to
change which control plane revision handles injection, it's possible to create a revision tag "prod" and label our
namespace "istio.io/rev=prod". The "prod" revision tag could point to "1-7-6" initially and then be changed to point to "1-8-1"
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 "istio.io/rev" 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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'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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></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></code></td><td></td><td>Name to use for a revision tag'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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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 "istio.io/rev" label. Verify that there are no remaining namespaces referencing a
revision tag before removing using the "istioctl tag list" 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></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></code></td><td></td><td>Name to use for a revision tag'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></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-r</code></td><td>Target control plane revision for the command. (default ``)</td></tr><tr><td><code>--set &lt;stringArray></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.16/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></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 uninstall --revision foo
# Uninstall a single control plane by iop file
istioctl uninstall -f iop.yaml
# Uninstall all control planes and shared resources
istioctl 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></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></code></td><td></td><td>XDS Endpoint certificate directory (default ``)</td></tr><tr><td><code>--context &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>One of 'yaml' or 'json'. (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></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></code></td><td></td><td>The duration to wait before failing (default `30s`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>XDS Endpoint (default ``)</td></tr><tr><td><code>--xds-label &lt;string></code></td><td></td><td>Istiod pod label selector (default ``)</td></tr><tr><td><code>--xds-port &lt;int></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--for &lt;string></code></td><td></td><td>Wait condition, must be 'distribution' or 'delete' (default `distribution`)</td></tr><tr><td><code>--generation &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--threshold &lt;float32></code></td><td></td><td>The ratio of distribution required for success (default `1`)</td></tr><tr><td><code>--timeout &lt;duration></code></td><td></td><td>The duration to wait before failing (default `30s`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The ID used to identify the cluster (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--externalIP &lt;string></code></td><td></td><td>External IP address of the workload (default ``)</td></tr><tr><td><code>--file &lt;string></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></code></td><td></td><td>IP address of the ingress gateway (default ``)</td></tr><tr><td><code>--ingressService &lt;string></code></td><td></td><td>Name of the Service to be used as the ingress gateway, in the format &lt;service>.&lt;namespace>. If no namespace is provided, the default istio-system namespace will be used. (default `istio-eastwestgateway`)</td></tr><tr><td><code>--internalIP &lt;string></code></td><td></td><td>Internal IP address of the workload (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--name &lt;string></code></td><td></td><td>The name of the workload group (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>Output directory for generated files (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--tokenDuration &lt;int></code></td><td></td><td>The token duration in seconds (default: 1 hour) (default `3600`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 'kubectl apply -f -' 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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--labels &lt;stringSlice></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></code></td><td></td><td>The name of the workload group (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--ports &lt;stringSlice></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></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></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--readiness-timeout &lt;duration></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></code></td><td><code>-r</code></td><td>Target control plane revision for the command. (default ``)</td></tr><tr><td><code>--set &lt;stringArray></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.16/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></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'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></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></code></td><td></td><td>XDS Endpoint certificate directory (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--filename &lt;string></code></td><td><code>-f</code></td><td>Input Kubernetes resource filename (default ``)</td></tr><tr><td><code>--injectConfigFile &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--meshConfigFile &lt;string></code></td><td></td><td>Mesh configuration filename. Takes precedence over --meshConfigMapName if set (default ``)</td></tr><tr><td><code>--meshConfigMapName &lt;string></code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--operatorFileName &lt;string></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></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></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--timeout &lt;duration></code></td><td></td><td>The duration to wait before failing (default `30s`)</td></tr><tr><td><code>--valuesFile &lt;string></code></td><td></td><td>Injection values configuration filename. (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>MutatingWebhookConfiguration name for Istio (default `istio-sidecar-injector`)</td></tr><tr><td><code>--xds-address &lt;string></code></td><td></td><td>XDS Endpoint (default ``)</td></tr><tr><td><code>--xds-label &lt;string></code></td><td></td><td>Istiod pod label selector (default ``)</td></tr><tr><td><code>--xds-port &lt;int></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 -> NEW-VALUE.
List order changes are shown as [OLD-INDEX->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></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--rename &lt;string></code></td><td></td><td>Rename resources before comparison.
The format of each renaming pair is A->B, all renaming pairs are comma separated.
e.g. Service:*:istiod->Service:*:istio-control - rename istiod service into istio-control (default ``)</td></tr><tr><td><code>--select &lt;string></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 "::" and the items are comma separated. The "*" character represents wildcard selection.
e.g.
Deployment:istio-system:* - compare all deployments in istio-system namespace
Service:*:istiod - compare Services called "istiod" 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></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--cluster-specific</code></td><td></td><td>If enabled, the current cluster will be checked for cluster-specific setting detection.</td></tr><tr><td><code>--component &lt;stringSlice></code></td><td></td><td>Specify which component to generate manifests for. (default `[]`)</td></tr><tr><td><code>--context &lt;string></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>Manifest output directory path. (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Target control plane revision for the command. (default ``)</td></tr><tr><td><code>--set &lt;stringArray></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.16/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec (default `[]`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--readiness-timeout &lt;duration></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></code></td><td><code>-r</code></td><td>Target control plane revision for the command. (default ``)</td></tr><tr><td><code>--set &lt;stringArray></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.16/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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></code></td><td></td><td>The hub for the operator controller image. (default `unknown`)</td></tr><tr><td><code>--imagePullSecrets &lt;stringSlice></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. '--imagePullSecrets imagePullSecret1,imagePullSecret2' (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--operatorNamespace &lt;string></code></td><td></td><td>The namespace the operator controller is installed into. (default `istio-operator`)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>Output format: one of json|yaml (default `yaml`)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Target revision for the operator. (default ``)</td></tr><tr><td><code>--tag &lt;string></code></td><td></td><td>The tag for the operator controller image. (default `unknown`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The namespaces the operator controller watches, could be namespace list separated by comma, eg. 'ns1,ns2' (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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></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></code></td><td></td><td>The hub for the operator controller image. (default `unknown`)</td></tr><tr><td><code>--imagePullSecrets &lt;stringSlice></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. '--imagePullSecrets imagePullSecret1,imagePullSecret2' (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--operatorNamespace &lt;string></code></td><td></td><td>The namespace the operator controller is installed into. (default `istio-operator`)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Target revision for the operator. (default ``)</td></tr><tr><td><code>--tag &lt;string></code></td><td></td><td>The tag for the operator controller image. (default `unknown`)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The namespaces the operator controller watches, could be namespace list separated by comma, eg. 'ns1,ns2' (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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--operatorNamespace &lt;string></code></td><td></td><td>The namespace the operator controller is installed into. (default `istio-operator`)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Target revision for the operator. (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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--config-path &lt;string></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></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>Filter listeners by address field (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--direction &lt;string></code></td><td></td><td>Filter clusters by Direction field (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump file (default ``)</td></tr><tr><td><code>--fqdn &lt;string></code></td><td></td><td>Filter clusters by substring of Service FQDN field (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--name &lt;string></code></td><td></td><td>Filter listeners by route name field (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td></td><td>Filter clusters and listeners by Port field (default `0`)</td></tr><tr><td><code>--subset &lt;string></code></td><td></td><td>Filter clusters by substring of Subset field (default ``)</td></tr><tr><td><code>--type &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--direction &lt;string></code></td><td></td><td>Filter clusters by Direction field (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--fqdn &lt;string></code></td><td></td><td>Filter clusters by substring of Service FQDN field (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td></td><td>Filter clusters by Port field (default `0`)</td></tr><tr><td><code>--subset &lt;string></code></td><td></td><td>Filter clusters by substring of Subset field (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Filter endpoints by address field (default ``)</td></tr><tr><td><code>--cluster &lt;string></code></td><td></td><td>Filter endpoints by cluster name field (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td></td><td>Filter endpoints by Port field (default `0`)</td></tr><tr><td><code>--status &lt;string></code></td><td></td><td>Filter endpoints by status field (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>Filter listeners by address field (default ``)</td></tr><tr><td><code>--context &lt;string></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td></td><td>Filter listeners by Port field (default `0`)</td></tr><tr><td><code>--type &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--level &lt;string></code></td><td></td><td>Comma-separated minimum per-logger level of messages to output, in the form of [&lt;logger>:]&lt;level>,[&lt;logger>:]&lt;level>,... 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></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></code></td><td><code>-l</code></td><td>Label selector (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--name &lt;string></code></td><td></td><td>Filter listeners by route name field (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--file &lt;string></code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 "istio.io/rev=revision-a" to "istio.io/rev=revision-b" to
change which control plane revision handles injection, it's possible to create a revision tag "prod" and label our
namespace "istio.io/rev=prod". The "prod" revision tag could point to "1-7-6" initially and then be changed to point to "1-8-1"
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 "istio.io/rev" 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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'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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></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></code></td><td></td><td>Name to use for a revision tag'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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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 "istio.io/rev" label. Verify that there are no remaining namespaces referencing a
revision tag before removing using the "istioctl tag list" 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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></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></code></td><td></td><td>Name to use for a revision tag'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-uninstall>istioctl uninstall</h2><p>The uninstall command uninstalls Istio from a cluster</p><pre class=language-bash><code>istioctl 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></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></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></code></td><td><code>-r</code></td><td>Target control plane revision for the command. (default ``)</td></tr><tr><td><code>--set &lt;stringArray></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.16/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></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-uninstall Examples">Examples</h3><pre class=language-bash><code> # Uninstall a single control plane by revision
istioctl uninstall --revision foo
# Uninstall a single control plane by iop file
istioctl uninstall -f iop.yaml
# Uninstall all control planes and shared resources
istioctl uninstall --purge
</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></code></td><td></td><td>Deprecated, use --manifests instead. (default ``)</td></tr><tr><td><code>--context &lt;string></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></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></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--readiness-timeout &lt;duration></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></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.16/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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--filename &lt;stringSlice></code></td><td><code>-f</code></td><td>Names of files to validate (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></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></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--filename &lt;stringSlice></code></td><td><code>-f</code></td><td>Istio YAML installation file. (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--manifests &lt;string></code></td><td><code>-d</code></td><td>Specify a path to a directory of charts and profiles
(e.g. ~/Downloads/istio-1.16.0/manifests)
or release tar URL (e.g. https://github.com/istio/istio/releases/download/1.16.0/istio-1.16.0-linux-amd64.tar.gz).
(default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--revision &lt;string></code></td><td><code>-r</code></td><td>Control plane revision (default ``)</td></tr><tr><td><code>--vklog &lt;Level></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></code></td><td></td><td>The name of the kubeconfig context to use (default ``)</td></tr><tr><td><code>--istioNamespace &lt;string></code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string></code></td><td><code>-c</code></td><td>Kubernetes configuration file (default ``)</td></tr><tr><td><code>--namespace &lt;string></code></td><td><code>-n</code></td><td>Config namespace (default ``)</td></tr><tr><td><code>--output &lt;string></code></td><td><code>-o</code></td><td>One of 'yaml' or 'json'. (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></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></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_ENHANCED_RESOURCE_SCOPING</code></td><td>Boolean</td><td><code>false</code></td><td>If enabled, meshConfig.discoverySelectors will limit the CustomResource configurations(like Gateway,VirtualService,DestinationRule,Ingress, etc)that can be processed by pilot. This will also restrict the root-ca certificate distribution.</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_LEADER_ELECTION</code></td><td>Boolean</td><td><code>true</code></td><td>If enabled (default), starts a leader election client and gains leadership before executing controllers. If false, it assumes that only one instance of istiod is running and skips leader election.</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 "first-party-jwt".</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>.&lt;namespace>.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>.&lt;namespace>.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' behaviors, but not kubelet'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_ENABLE_HTTP2_PROBING</code></td><td>Boolean</td><td><code>true</code></td><td>If enabled, HTTP2 probes will be enabled for HTTPS probes, following Kubernetes</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_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_ALLOW_SIDECAR_SERVICE_INBOUND_LISTENER_MERGE</code></td><td>Boolean</td><td><code>false</code></td><td>If set, it allows creating inbound listeners for service ports and sidecar ingress listeners</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'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'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_DRAINING_LABEL</code></td><td>String</td><td><code>istio.io/draining</code></td><td>If not empty, endpoints with the label value present will be sent with status DRAINING.</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_HBONE</code></td><td>Boolean</td><td><code>false</code></td><td>If enabled, HBONE support can be configured for proxies. Note: proxies must opt in on a per-proxy basis with ENABLE_HBONE to actually get HBONE config, in addition to this flag.</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'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'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'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_PERSISTENT_SESSION_LABEL</code></td><td>String</td><td><code>istio.io/persistent-session</code></td><td>If not empty, services with this label will use persistent sessions</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>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 'localhost'. Otherwise, they will be sent to the Pod's IP, matching Kubernetes' 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>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>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> 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>TELEMETRY_USE_NATIVE_STATS</code></td><td>Boolean</td><td><code>false</code></td><td>True if the stats runtime should use the Envoy extension instead of the compiled Wasm extension.</td></tr><tr><td><code>TERM</code></td><td>String</td><td><code></code></td><td>Specifies terminal type. Use 'dumb' 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 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>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_debounce_time</code></td><td><code>Distribution</code></td><td>Delay in seconds between the first config enters debouncing and the merged push request is pushed into the push queue.</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_pushcontext_init_seconds</code></td><td><code>Distribution</code></td><td>Total time in seconds Pilot takes to init pushContext.</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_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>reconcile_request_total</code></td><td><code>Sum</code></td><td>Number of times requesting Reconcile</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></tbody></table></article><nav class=pagenav><div class=left><a title="Install and configure Istio CNI plugin on a node, detect and repair pod which is broken by race condition." href=/v1.16/zh/docs/reference/commands/install-cni/ class=next-link><svg class="icon left-arrow"><use xlink:href="/v1.16/img/icons.svg#left-arrow"/></svg>install-cni</a></div><div class=right><a title="The Istio operator." href=/v1.16/zh/docs/reference/commands/operator/ class=next-link>operator<svg class="icon right-arrow"><use xlink:href="/v1.16/img/icons.svg#right-arrow"/></svg></a></div></nav><div id=feedback><div id=feedback-initial>这些信息有用吗？<br><button class="btn feedback" onclick='sendFeedback("zh",1)'>是的</button>
<button class="btn feedback" onclick='sendFeedback("zh",0)'>没有</button></div><div id=feedback-comment>Do you have any suggestions for improvement?<br><br><input id=feedback-textbox type=text placeholder='Help us improve...' data-lang=zh></div><div id=feedback-thankyou>Thanks for your feedback!</div></div><div id=endnotes-container aria-hidden=true><h2>链接</h2><ol id=endnotes></ol></div></div><div class=toc-container><nav class=toc aria-label="Table of Contents"><div id=toc><ol><li role=none aria-label="istioctl admin"><a href=#istioctl-admin>admin</a><li role=none aria-label="istioctl admin log"><a href=#istioctl-admin-log>admin log</a><li role=none aria-label="istioctl analyze"><a href=#istioctl-analyze>analyze</a><li role=none aria-label="istioctl authz"><a href=#istioctl-authz>authz</a><li role=none aria-label="istioctl bug-report"><a href=#istioctl-bug-report>bug-report</a><li role=none aria-label="istioctl bug-report version"><a href=#istioctl-bug-report-version>bug-report version</a><li role=none aria-label="istioctl completion"><a href=#istioctl-completion>completion</a><li role=none aria-label="istioctl completion bash"><a href=#istioctl-completion-bash>completion bash</a><li role=none aria-label="istioctl completion fish"><a href=#istioctl-completion-fish>completion fish</a><li role=none aria-label="istioctl completion powershell"><a href=#istioctl-completion-powershell>completion powershell</a><li role=none aria-label="istioctl completion zsh"><a href=#istioctl-completion-zsh>completion zsh</a><li role=none aria-label="istioctl dashboard"><a href=#istioctl-dashboard>dashboard</a><li role=none aria-label="istioctl dashboard controlz"><a href=#istioctl-dashboard-controlz>dashboard controlz</a><li role=none aria-label="istioctl dashboard envoy"><a href=#istioctl-dashboard-envoy>dashboard envoy</a><li role=none aria-label="istioctl dashboard grafana"><a href=#istioctl-dashboard-grafana>dashboard grafana</a><li role=none aria-label="istioctl dashboard jaeger"><a href=#istioctl-dashboard-jaeger>dashboard jaeger</a><li role=none aria-label="istioctl dashboard kiali"><a href=#istioctl-dashboard-kiali>dashboard kiali</a><li role=none aria-label="istioctl dashboard prometheus"><a href=#istioctl-dashboard-prometheus>dashboard prometheus</a><li role=none aria-label="istioctl dashboard skywalking"><a href=#istioctl-dashboard-skywalking>dashboard skywalking</a><li role=none aria-label="istioctl dashboard zipkin"><a href=#istioctl-dashboard-zipkin>dashboard zipkin</a><li role=none aria-label="istioctl experimental"><a href=#istioctl-experimental>experimental</a><li role=none aria-label="istioctl experimental add-to-mesh"><a href=#istioctl-experimental-add-to-mesh>experimental add-to-mesh</a><li role=none aria-label="istioctl experimental add-to-mesh deployment"><a href=#istioctl-experimental-add-to-mesh-deployment>experimental add-to-mesh deployment</a><li role=none aria-label="istioctl experimental add-to-mesh external-service"><a href=#istioctl-experimental-add-to-mesh-external-service>experimental add-to-mesh external-service</a><li role=none aria-label="istioctl experimental add-to-mesh service"><a href=#istioctl-experimental-add-to-mesh-service>experimental add-to-mesh service</a><li role=none aria-label="istioctl experimental authz"><a href=#istioctl-experimental-authz>experimental authz</a><li role=none aria-label="istioctl experimental authz check"><a href=#istioctl-experimental-authz-check>experimental authz check</a><li role=none aria-label="istioctl experimental check-inject"><a href=#istioctl-experimental-check-inject>experimental check-inject</a><li role=none aria-label="istioctl experimental config"><a href=#istioctl-experimental-config>experimental config</a><li role=none aria-label="istioctl experimental config list"><a href=#istioctl-experimental-config-list>experimental config list</a><li role=none aria-label="istioctl experimental create-remote-secret"><a href=#istioctl-experimental-create-remote-secret>experimental create-remote-secret</a><li role=none aria-label="istioctl experimental describe"><a href=#istioctl-experimental-describe>experimental describe</a><li role=none aria-label="istioctl experimental describe pod"><a href=#istioctl-experimental-describe-pod>experimental describe pod</a><li role=none aria-label="istioctl experimental describe service"><a href=#istioctl-experimental-describe-service>experimental describe service</a><li role=none aria-label="istioctl experimental envoy-stats"><a href=#istioctl-experimental-envoy-stats>experimental envoy-stats</a><li role=none aria-label="istioctl experimental injector"><a href=#istioctl-experimental-injector>experimental injector</a><li role=none aria-label="istioctl experimental injector list"><a href=#istioctl-experimental-injector-list>experimental injector list</a><li role=none aria-label="istioctl experimental internal-debug"><a href=#istioctl-experimental-internal-debug>experimental internal-debug</a><li role=none aria-label="istioctl experimental kube-uninject"><a href=#istioctl-experimental-kube-uninject>experimental kube-uninject</a><li role=none aria-label="istioctl experimental metrics"><a href=#istioctl-experimental-metrics>experimental metrics</a><li role=none aria-label="istioctl experimental precheck"><a href=#istioctl-experimental-precheck>experimental precheck</a><li role=none aria-label="istioctl experimental proxy-status"><a href=#istioctl-experimental-proxy-status>experimental proxy-status</a><li role=none aria-label="istioctl experimental remote-clusters"><a href=#istioctl-experimental-remote-clusters>experimental remote-clusters</a><li role=none aria-label="istioctl experimental remove-from-mesh"><a href=#istioctl-experimental-remove-from-mesh>experimental remove-from-mesh</a><li role=none aria-label="istioctl experimental remove-from-mesh deployment"><a href=#istioctl-experimental-remove-from-mesh-deployment>experimental remove-from-mesh deployment</a><li role=none aria-label="istioctl experimental remove-from-mesh external-service"><a href=#istioctl-experimental-remove-from-mesh-external-service>experimental remove-from-mesh external-service</a><li role=none aria-label="istioctl experimental remove-from-mesh service"><a href=#istioctl-experimental-remove-from-mesh-service>experimental remove-from-mesh service</a><li role=none aria-label="istioctl experimental revision"><a href=#istioctl-experimental-revision>experimental revision</a><li role=none aria-label="istioctl experimental revision describe"><a href=#istioctl-experimental-revision-describe>experimental revision describe</a><li role=none aria-label="istioctl experimental revision list"><a href=#istioctl-experimental-revision-list>experimental revision list</a><li role=none aria-label="istioctl experimental revision tag"><a href=#istioctl-experimental-revision-tag>experimental revision tag</a><li role=none aria-label="istioctl experimental revision tag generate"><a href=#istioctl-experimental-revision-tag-generate>experimental revision tag generate</a><li role=none aria-label="istioctl experimental revision tag list"><a href=#istioctl-experimental-revision-tag-list>experimental revision tag list</a><li role=none aria-label="istioctl experimental revision tag remove"><a href=#istioctl-experimental-revision-tag-remove>experimental revision tag remove</a><li role=none aria-label="istioctl experimental revision tag set"><a href=#istioctl-experimental-revision-tag-set>experimental revision tag set</a><li role=none aria-label="istioctl experimental uninstall"><a href=#istioctl-experimental-uninstall>experimental uninstall</a><li role=none aria-label="istioctl experimental version"><a href=#istioctl-experimental-version>experimental version</a><li role=none aria-label="istioctl experimental wait"><a href=#istioctl-experimental-wait>experimental wait</a><li role=none aria-label="istioctl experimental workload"><a href=#istioctl-experimental-workload>experimental workload</a><li role=none aria-label="istioctl experimental workload entry"><a href=#istioctl-experimental-workload-entry>experimental workload entry</a><li role=none aria-label="istioctl experimental workload entry configure"><a href=#istioctl-experimental-workload-entry-configure>experimental workload entry configure</a><li role=none aria-label="istioctl experimental workload group"><a href=#istioctl-experimental-workload-group>experimental workload group</a><li role=none aria-label="istioctl experimental workload group create"><a href=#istioctl-experimental-workload-group-create>experimental workload group create</a><li role=none aria-label="istioctl install"><a href=#istioctl-install>install</a><li role=none aria-label="istioctl kube-inject"><a href=#istioctl-kube-inject>kube-inject</a><li role=none aria-label="istioctl manifest"><a href=#istioctl-manifest>manifest</a><li role=none aria-label="istioctl manifest diff"><a href=#istioctl-manifest-diff>manifest diff</a><li role=none aria-label="istioctl manifest generate"><a href=#istioctl-manifest-generate>manifest generate</a><li role=none aria-label="istioctl manifest install"><a href=#istioctl-manifest-install>manifest install</a><li role=none aria-label="istioctl operator"><a href=#istioctl-operator>operator</a><li role=none aria-label="istioctl operator dump"><a href=#istioctl-operator-dump>operator dump</a><li role=none aria-label="istioctl operator init"><a href=#istioctl-operator-init>operator init</a><li role=none aria-label="istioctl operator remove"><a href=#istioctl-operator-remove>operator remove</a><li role=none aria-label="istioctl options"><a href=#istioctl-options>options</a><li role=none aria-label="istioctl profile"><a href=#istioctl-profile>profile</a><li role=none aria-label="istioctl profile diff"><a href=#istioctl-profile-diff>profile diff</a><li role=none aria-label="istioctl profile dump"><a href=#istioctl-profile-dump>profile dump</a><li role=none aria-label="istioctl profile list"><a href=#istioctl-profile-list>profile list</a><li role=none aria-label="istioctl proxy-config"><a href=#istioctl-proxy-config>proxy-config</a><li role=none aria-label="istioctl proxy-config all"><a href=#istioctl-proxy-config-all>proxy-config all</a><li role=none aria-label="istioctl proxy-config bootstrap"><a href=#istioctl-proxy-config-bootstrap>proxy-config bootstrap</a><li role=none aria-label="istioctl proxy-config cluster"><a href=#istioctl-proxy-config-cluster>proxy-config cluster</a><li role=none aria-label="istioctl proxy-config endpoint"><a href=#istioctl-proxy-config-endpoint>proxy-config endpoint</a><li role=none aria-label="istioctl proxy-config listener"><a href=#istioctl-proxy-config-listener>proxy-config listener</a><li role=none aria-label="istioctl proxy-config log"><a href=#istioctl-proxy-config-log>proxy-config log</a><li role=none aria-label="istioctl proxy-config rootca-compare"><a href=#istioctl-proxy-config-rootca-compare>proxy-config rootca-compare</a><li role=none aria-label="istioctl proxy-config route"><a href=#istioctl-proxy-config-route>proxy-config route</a><li role=none aria-label="istioctl proxy-config secret"><a href=#istioctl-proxy-config-secret>proxy-config secret</a><li role=none aria-label="istioctl proxy-status"><a href=#istioctl-proxy-status>proxy-status</a><li role=none aria-label="istioctl tag"><a href=#istioctl-tag>tag</a><li role=none aria-label="istioctl tag generate"><a href=#istioctl-tag-generate>tag generate</a><li role=none aria-label="istioctl tag list"><a href=#istioctl-tag-list>tag list</a><li role=none aria-label="istioctl tag remove"><a href=#istioctl-tag-remove>tag remove</a><li role=none aria-label="istioctl tag set"><a href=#istioctl-tag-set>tag set</a><li role=none aria-label="istioctl uninstall"><a href=#istioctl-uninstall>uninstall</a><li role=none aria-label="istioctl upgrade"><a href=#istioctl-upgrade>upgrade</a><li role=none aria-label="istioctl validate"><a href=#istioctl-validate>validate</a><li role=none aria-label="istioctl verify-install"><a href=#istioctl-verify-install>verify-install</a><li role=none aria-label="istioctl version"><a href=#istioctl-version>version</a><li role=none aria-label="Environment variables"><a href=#envvars>Environment variables</a><li role=none aria-label="Exported metrics"><a href=#metrics>Exported metrics</a></ol></div></nav></div></main><footer class=footer><div class="footer-wrapper container-l"><div class="user-links footer-links"><a class=channel title='Istio 的代码在 GitHub 上开发' href=https://github.com/istio/community aria-label=GitHub><svg class="icon github"><use xlink:href="/v1.16/img/icons.svg#github"/></svg></a><a class=channel title='如果您想深入了解 Istio 的技术细节，请查看我们日益完善的设计文档' href=https://groups.google.com/forum/#!forum/istio-team-drive-access aria-label="team drive"><svg class="icon drive"><use xlink:href="/v1.16/img/icons.svg#drive"/></svg></a><a class=channel title='在 Slack 上与 Istio 社区交互讨论开发问题（仅限邀请）' href=https://slack.istio.io aria-label=slack><svg class="icon slack"><use xlink:href="/v1.16/img/icons.svg#slack"/></svg></a><a class=channel title='Stack Overflow 中列举了针对实际问题以及部署、配置和使用 Istio 的各项回答' href=https://stackoverflow.com/questions/tagged/istio aria-label="Stack Overflow"><svg class="icon stackoverflow"><use xlink:href="/v1.16/img/icons.svg#stackoverflow"/></svg></a><a class=channel title='关注我们的 Twitter 来获取最新信息' href=https://twitter.com/IstioMesh aria-label=Twitter><svg class="icon twitter"><use xlink:href="/v1.16/img/icons.svg#twitter"/></svg></a></div><hr class=footer-separator role=separator><div class="info footer-info"><a class=logo href=/v1.16/zh/ aria-label=logotype><svg xmlns="http://www.w3.org/2000/svg" width="128" height="60" viewBox="0 0 128 60"><path d="M58.434 48.823A.441.441.0 0158.3 48.497V22.583a.444.444.0 01.134-.326.446.446.0 01.327-.134h3.527a.447.447.0 01.325.134.447.447.0 01.134.326v25.914a.443.443.0 01-.134.326.444.444.0 01-.325.134h-3.527a.444.444.0 01-.327-.134z"/><path d="m70.969 48.477a6.556 6.556.0 01-2.818-1.955 4.338 4.338.0 01-1-2.78v-.345a.443.443.0 01.134-.326.444.444.0 01.326-.135h3.374a.444.444.0 01.326.135.445.445.0 01.134.326v.077a2.014 2.014.0 001.054 1.667 4.672 4.672.0 002.664.709 4.446 4.446.0 002.492-.633 1.862 1.862.0 00.958-1.591 1.426 1.426.0 00-.786-1.322 12.7 12.7.0 00-2.549-.939l-1.457-.46a21.526 21.526.0 01-3.3-1.227 6.57 6.57.0 01-2.262-1.783 4.435 4.435.0 01-.92-2.894 5.081 5.081.0 012.109-4.275 8.993 8.993.0 015.558-1.591 10.445 10.445.0 014.1.748 6.3 6.3.0 012.722 2.07 5 5 0 01.958 3.009.441.441.0 01-.134.326.441.441.0 01-.325.134h-3.258a.441.441.0 01-.326-.134.443.443.0 01-.134-.326 1.974 1.974.0 00-.978-1.667 4.647 4.647.0 00-2.665-.671 4.741 4.741.0 00-2.435.556 1.724 1.724.0 00-.938 1.553 1.512 1.512.0 00.9 1.4 15.875 15.875.0 003.01 1.055l.843.229a27.368 27.368.0 013.412 1.246 6.67 6.67.0 012.338 1.763 4.387 4.387.0 01.958 2.933 4.988 4.988.0 01-2.146 4.275 9.543 9.543.0 01-5.712 1.552 11.626 11.626.0 01-4.227-.709z"/><path d="m97.039 32.837a.443.443.0 01-.326.135h-3.911a.169.169.0 00-.191.192v9.239a2.951 2.951.0 00.632 2.108 2.7 2.7.0 002.013.652h1.15a.444.444.0 01.325.134.441.441.0 01.134.326v2.875a.471.471.0 01-.459.5l-1.994.039a8 8 0 01-4.524-1.035q-1.495-1.035-1.533-3.91V33.166A.17.17.0 0088.164 32.974H85.978A.441.441.0 0185.652 32.839.441.441.0 0185.518 32.513V29.83a.441.441.0 01.134-.326.444.444.0 01.326-.135h2.186a.169.169.0 00.191-.192v-4.485a.438.438.0 01.134-.326.44.44.0 01.325-.134h3.336a.443.443.0 01.325.134.442.442.0 01.135.326v4.485a.169.169.0 00.191.192h3.911a.446.446.0 01.326.135.446.446.0 01.134.326v2.683a.446.446.0 01-.133.324z"/><path d="m101.694 25.917a2.645 2.645.0 01-.767-1.955 2.65 2.65.0 01.767-1.955 2.65 2.65.0 011.955-.767 2.65 2.65.0 011.955.767 2.652 2.652.0 01.767 1.955 2.647 2.647.0 01-.767 1.955 2.646 2.646.0 01-1.955.767 2.645 2.645.0 01-1.955-.767zm-.211 22.906a.441.441.0 01-.134-.326V29.79a.444.444.0 01.134-.326.446.446.0 01.326-.134h3.527a.446.446.0 01.326.134.445.445.0 01.134.326v18.707a.443.443.0 01-.134.326.443.443.0 01-.326.134h-3.527a.443.443.0 01-.326-.134z"/><path d="m114.019 47.734a8.1 8.1.0 01-3.047-4.255 14.439 14.439.0 01-.652-4.37 14.3 14.3.0 01.614-4.371A7.869 7.869.0 01114 30.56a9.072 9.072.0 015.252-1.5 8.543 8.543.0 015.041 1.5 7.985 7.985.0 013.009 4.14 12.439 12.439.0 01.69 4.37 13.793 13.793.0 01-.651 4.37 8.255 8.255.0 01-3.028 4.275 8.475 8.475.0 01-5.1 1.553 8.754 8.754.0 01-5.194-1.534zm7.629-3.1a4.536 4.536.0 001.476-2.262 11.335 11.335.0 00.383-3.221 10.618 10.618.0 00-.383-3.22 4.169 4.169.0 00-1.457-2.243 4.066 4.066.0 00-2.531-.785 3.942 3.942.0 00-2.453.785 4.376 4.376.0 00-1.5 2.243 11.839 11.839.0 00-.383 3.22 11.84 11.84.0 00.383 3.221 4.222 4.222.0 001.476 2.262 4.075 4.075.0 002.549.8 3.8 3.8.0 002.44-.809z"/><path d="m15.105 32.057v15.565a.059.059.0 01-.049.059L.069 50.25A.06.06.0 01.005 50.167l14.987-33.47a.06.06.0 01.114.025z"/><path d="m17.631 23.087v24.6a.06.06.0 00.053.059l22.449 2.507a.06.06.0 00.061-.084L17.745.032a.06.06.0 00-.114.024z"/><path d="m39.961 52.548-24.833 7.45a.062.062.0 01-.043.0L.079 52.548a.059.059.0 01.026-.113h39.839a.06.06.0 01.017.113z"/></svg></a><div class=footer-languages><a tabindex=-1 lang=en id=switch-lang-en class=footer-languages-item>English</a>
<a tabindex=-1 lang=zh id=switch-lang-zh class="footer-languages-item active"><svg class="icon tick"><use xlink:href="/v1.16/img/icons.svg#tick"/></svg>中文</a></div></div><ul class=footer-policies><li class=footer-policies-item><a class=footer-policies-link href=https://www.linuxfoundation.org/legal/terms>条款</a> |
<a class=footer-policies-link href=https://www.linuxfoundation.org/legal/privacy-policy>隐私政策</a> |
<a class=disabled title="这是一个自动生成的文件，要修改其中的内容，请修改 https://github.com/istio/istio 仓库中的源码。">在 GitHub 上编辑此页</a></li></ul><div class=footer-base><span class=footer-base-copyright>&copy; 2023 the Istio Authors.</span>
<span class=footer-base-version>部分内容可能滞后于英文版本，同步工作正在进行中<br>Version
Istio 归档
1.16.2</span><ul class=footer-base-releases><li class=footer-base-releases-item><a tabindex=-1 class=footer-base-releases-link onclick='return navigateToUrlOrRoot("https://istio.io/docs/reference/commands/istioctl/"),!1'>当前版本</a></li><li class=footer-base-releases-item><a tabindex=-1 class=footer-base-releases-link onclick='return navigateToUrlOrRoot("https://preliminary.istio.io/docs/reference/commands/istioctl/"),!1'>下个版本</a></li><li class=footer-base-releases-item><a tabindex=-1 class=footer-base-releases-link href=https://istio.io/archive>旧版本</a></li></ul></div></div></footer><div id=scroll-to-top-container aria-hidden=true><button id=scroll-to-top title=回到顶部 tabindex=-1><svg class="icon top"><use xlink:href="/v1.16/img/icons.svg#top"/></svg></button></div></body></html>
Reference in New Issue View Git Blame Copy Permalink