istioctl

    Analyze Istio configuration and print validation messages

    FlagsShorthandDescription
    —all-namespacesAnalyze all namespaces
    —colorDefault true. Disable with ‘=false’ or set $TERM to dumb
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--discovery</code></td><td><code>-d</code></td><td>'true' to enable service discovery, 'false' to disable it. Defaults to true if --use-kube is set, false otherwise. Analyzers requiring resources made available by enabling service discovery will be skipped.</td></tr><tr><td><code>--failure-threshold &lt;Level&gt;</code></td><td></td><td>The severity level of analysis at which to set a non-zero exit code. Valid values: [Info Warn Error] (default `Warn`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —list-analyzers-LList the analyzers available to run. Suppresses normal execution.
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —meshConfigFile <string>Overrides the mesh config values to use for analysis. (default )</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of [log json yaml] (default log)
    —output-threshold <Level>The severity level of analysis at which to display messages. Valid values: [Info Warn Error] (default Info)
    —use-kube-kUse live Kubernetes cluster for analysis
    —verbose-vEnable verbose output
    1. # Analyze yaml files
    2. istioctl analyze a.yaml b.yaml
    3. # Analyze the current live cluster
    4. istioctl analyze -k
    5. # Analyze the current live cluster, simulating the effect of applying additional yaml files
    6. istioctl analyze -k a.yaml b.yaml
    7. # Analyze yaml files, overriding service discovery to enabled
    8. istioctl analyze -d true a.yaml b.yaml services.yaml
    9. # Analyze the current live cluster, overriding service discovery to disabled
    10. istioctl analyze -k -d false
    11. # List available analyzers
    12. istioctl analyze -L

    istioctl authn

    A group of commands used to interact with Istio authentication policies. tls-check

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. # Check whether TLS setting are matching between authentication policy and destination rules:
    2. istioctl authn tls-check

    istioctl authn tls-check

    Check what authentication policies and destination rules pilot uses to config a proxy instance, and check if TLS settings are compatible between them.

    1. istioctl authn tls-check <pod-name[.namespace]> [<service>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. # Check settings for pod "foo-656bd7df7c-5zp4s" in namespace default:
    2. istioctl authn tls-check foo-656bd7df7c-5zp4s.default
    3. # Check settings for pod "foo-656bd7df7c-5zp4s" in namespace default, filtered on destination
    4. service "bar" :
    5. istioctl authn tls-check foo-656bd7df7c-5zp4s.default bar

    istioctl authz

    (authz is experimental. Use `istioctl experimental authz`)

    1. istioctl authz [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl convert-ingress

    Converts Ingresses into VirtualService configuration on a best effort basis. The output should be considered a starting point for your Istio configuration and probably require some minor modification. Warnings will be generated where configs cannot be converted perfectly. The input must be a Kubernetes Ingress. The conversion of v1alpha1 Istio rules has been removed from istioctl.

    1. istioctl convert-ingress [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filenames &lt;stringSlice&gt;</code></td><td><code>-f</code></td><td>Input filenames (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--output &lt;string&gt;</code></td><td><code>-o</code></td><td>Output filename (default-`)

    Examples

    1. istioctl convert-ingress -f samples/bookinfo/platform/kube/bookinfo-ingress.yaml

    istioctl dashboard

    Access to Istio web UIs

    1. istioctl dashboard [flags]
    1. istioctl dash [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl dashboard controlz

    Open the ControlZ web UI for a pod in the Istio control plane

    1. istioctl dashboard controlz <pod-name[.namespace]> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--ctrlz_port &lt;int&gt;</code></td><td></td><td>ControlZ port (default `9876`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--selector &lt;string&gt;</code></td><td><code>-l</code></td><td>label selector (default)

    Examples

    1. istioctl dashboard controlz pilot-123-456.istio-system

    istioctl dashboard envoy

    Open the Envoy admin dashboard for a sidecar

    1. istioctl dashboard envoy <pod-name[.namespace]> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--selector &lt;string&gt;</code></td><td><code>-l</code></td><td>label selector (default)

    Examples

    1. istioctl dashboard envoy productpage-123-456.default

    istioctl dashboard grafana

    Open Istio’s Grafana dashboard

    1. istioctl dashboard grafana [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl dashboard grafana

    istioctl dashboard jaeger

    Open Istio’s Jaeger dashboard

    1. istioctl dashboard jaeger [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl dashboard jaeger

    istioctl dashboard kiali

    Open Istio’s Kiali dashboard

    1. istioctl dashboard kiali [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl dashboard kiali

    istioctl dashboard prometheus

    Open Istio’s Prometheus dashboard

    1. istioctl dashboard prometheus [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl dashboard prometheus

    istioctl dashboard zipkin

    Open Istio’s Zipkin dashboard

    1. istioctl dashboard zipkin [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl dashboard zipkin

    istioctl deregister

    De-registers a service instance

    1. istioctl deregister <svcname> <ip> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. # de-register an endpoint 172.17.0.2 from service my-svc:
    2. istioctl deregister my-svc 172.17.0.2

    istioctl experimental

    Experimental commands that may be modified or deprecated

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental add-to-mesh

    Add workloads into Istio service mesh

    1. istioctl experimental add-to-mesh [flags]
    1. istioctl experimental add [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental add-to-mesh external-service

    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. THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental add-to-mesh external-service <svcname> <ip>... [name1:]port1 [name2:]port2 ... [flags]
    FlagsShorthandDescription
    —annotations <stringSlice>-aList of string annotations to apply if creating a service/endpoint; e.g. -a foo=bar,x=y (default [])
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —labels <stringSlice>-lList of labels to apply if creating a service/endpoint; e.g. -l env=prod,vers=2 (default [])
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--serviceaccount &lt;string&gt;</code></td><td><code>-s</code></td><td>Service account to link to the service (defaultdefault`)

    Examples

    1. istioctl experimental add-to-mesh external-service vmhttp 172.12.23.125,172.12.23.126\
    2. http:9080 tcp:8888 -l app=test,version=v1 -a env=stage -s stageAdmin

    istioctl experimental add-to-mesh service

    istioctl experimental add-to-mesh service restarts pods with the Istio sidecar. Use ‘add-to-mesh’ to test deployments for compatibility with Istio. If your service does not function after using ‘add-to-mesh’ you must re-deploy it and troubleshoot it for Istio compatibility. See THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental add-to-mesh service [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--injectConfigFile &lt;string&gt;</code></td><td></td><td>injection configuration filename. Cannot be used with --injectConfigMapName (default)
    —injectConfigMapName <string>ConfigMap name for Istio sidecar injection, key should be “config”. (default istio-sidecar-injector)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--meshConfigFile &lt;string&gt;</code></td><td></td><td>mesh configuration filename. Takes precedence over --meshConfigMapName if set (default)
    —meshConfigMapName <string>ConfigMap name for Istio mesh configuration, key should be “mesh” (default istio)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--valuesFile &lt;string&gt;</code></td><td></td><td>injection values configuration filename. (default)
    1. istioctl experimental add-to-mesh service productpage

    istioctl experimental analyze

    Analyze Istio configuration and print validation messages (analyze has graduated. Use `istioctl analyze`)

    1. istioctl experimental analyze <file>... [flags]
    FlagsShorthandDescription
    —all-namespacesAnalyze all namespaces
    —colorDefault true. Disable with ‘=false’ or set $TERM to dumb
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--discovery</code></td><td><code>-d</code></td><td>'true' to enable service discovery, 'false' to disable it. Defaults to true if --use-kube is set, false otherwise. Analyzers requiring resources made available by enabling service discovery will be skipped.</td></tr><tr><td><code>--failure-threshold &lt;Level&gt;</code></td><td></td><td>The severity level of analysis at which to set a non-zero exit code. Valid values: [Info Warn Error] (default `Warn`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —list-analyzers-LList the analyzers available to run. Suppresses normal execution.
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —meshConfigFile <string>Overrides the mesh config values to use for analysis. (default )</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of [yaml log json] (default log)
    —output-threshold <Level>The severity level of analysis at which to display messages. Valid values: [Info Warn Error] (default Info)
    —use-kube-kUse live Kubernetes cluster for analysis
    —verbose-vEnable verbose output

    Examples

    1. # Analyze yaml files
    2. istioctl analyze a.yaml b.yaml
    3. # Analyze the current live cluster
    4. istioctl analyze -k
    5. # Analyze the current live cluster, simulating the effect of applying additional yaml files
    6. istioctl analyze -k a.yaml b.yaml
    7. # Analyze yaml files, overriding service discovery to enabled
    8. istioctl analyze -d true a.yaml b.yaml services.yaml
    9. # Analyze the current live cluster, overriding service discovery to disabled
    10. istioctl analyze -k -d false
    11. # List available analyzers
    12. istioctl analyze -L

    istioctl experimental authz

    Commands to inspect and interact with the authorization policies check - check Envoy config dump for authorization configuration convert - convert v1alpha1 RBAC policies to v1beta1 authorization policies

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. # Check Envoy authorization configuration for pod httpbin-88ddbcfdd-nt5jb:
    2. istioctl x authz check httpbin-88ddbcfdd-nt5jb
    3. # Convert the v1alpha1 RBAC policies in the current cluster to v1beta1 authorization policies:
    4. istioctl x authz convert > v1beta1-authz.yaml

    istioctl experimental authz check

    Check reads the Envoy config dump and checks the filter configuration related to authorization. For example, it shows whether or not the Envoy is configured with authorization and the rules used in the authorization.

    The Envoy config dump could be provided either by pod name or from a config dump file (the whole output of of an Envoy instance).

    THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental authz check <pod-name>[.<pod-namespace>] [flags]
    FlagsShorthandDescription
    —all-aShow additional information (e.g. SNI and ALPN)
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;string&gt;</code></td><td><code>-f</code></td><td>Check the Envoy config dump from a file (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)

    Examples

    1. # Check Envoy authorization configuration for pod httpbin-88ddbcfdd-nt5jb:
    2. istioctl x authz check httpbin-88ddbcfdd-nt5jb
    3. # Check Envoy authorization configuration from a config dump file:
    4. istioctl x authz check -f httpbin_config_dump.json

    istioctl experimental authz convert

    Convert Istio v1alpha1 RBAC policy to v1beta1 authorization policy. The command talks to Kubernetes API server to get all the information needed to complete the conversion, including the v1alpha1 RBAC policies in the current cluster, the Istio config-map for root namespace configuration and the k8s Service translating the service name to workload selector.

    The tool can also be used in offline mode without talking to the Kubernetes API server. In this mode, all needed information is provided through the command line.

    Note: The converter tool makes a best effort attempt to keep the syntax unchanged when converting v1alph1 RBAC policy to v1beta1 policy. However, in some cases, strict mapping with equivalent syntax is not possible (e.g., constraints no longer valid in the new workload oriented model, converting a service name containing a wildcard to workload selector).

    THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental authz convert [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;stringSlice&gt;</code></td><td><code>-f</code></td><td>v1alpha1 RBAC policy that needs to be converted to v1beta1 authorization policy (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —meshConfigFile <string>-mIstio MeshConfig file that provides the root namespace value (default )</td></tr><tr><td><code>--meshConfigMapName &lt;string&gt;</code></td><td></td><td>ConfigMap name for Istio mesh configuration (default `istio`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —service <stringSlice>-sKubernetes Service resource that provides the mapping between service and workload (default [])

    Examples

    istioctl experimental convert-ingress

    (convert-ingress has graduated. Use `istioctl convert-ingress`)

    1. istioctl experimental convert-ingress [flags]

    Create a secret with credentials to allow Istio to access remote Kubernetes apiservers

    1. istioctl experimental create-remote-secret <cluster-name> [flags]
    FlagsShorthandDescription
    —auth-plugin-config <stringToString>authenticator plug-in configuration. —auth-type=plugin must be set with this option (default [])
    —auth-plugin-name <string>authenticator plug-in name. —auth-type=plugin must be set with this option (default )</td></tr><tr><td><code>--auth-type &lt;RemoteSecretAuthType&gt;</code></td><td></td><td>type of authentication to use. supported values = [bearer-token plugin] (default `bearer-token`)</td></tr><tr><td><code>--context &lt;string&gt;</code></td><td></td><td>The name of the kubeconfig context to use (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —service-account <string>create a secret with this service account’s credentials. (default istio-reader-service-account)

    Examples

    1. # Create a secret to access cluster c0's apiserver and install it in cluster c1.
    2. istioctl --Kubeconfig=c0.yaml x create-remote-secret \
    3. | kubectl -n istio-system --Kubeconfig=c1.yaml apply -f -
    4. # Delete a secret that was previously installed in c1
    5. istioctl --Kubeconfig=c0.yaml x create-remote-secret \
    6. | kubectl -n istio-system --Kubeconfig=c1.yaml delete -f -
    7. # Create a secret access a remote cluster with an auth plugin
    8. istioctl --Kubeconfig=c0.yaml x create-remote-secret --auth-type=plugin --auth-plugin-name=gcp \
    9. | kubectl -n istio-system --Kubeconfig=c1.yaml apply -f -

    istioctl experimental dashboard

    (dashboard has graduated. Use `istioctl dashboard`)

    1. istioctl experimental dashboard [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental describe

    Describe resource and related Istio configuration

    1. istioctl experimental describe [flags]
    1. istioctl experimental des [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental describe pod

    Analyzes pod, its Services, DestinationRules, and VirtualServices and reports the configuration objects that affect that pod.

    THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental describe pod <pod> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--ignoreUnmeshed</code></td><td></td><td>Suppress warnings for unmeshed pods</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl experimental describe pod productpage-v1-c7765c886-7zzd4

    istioctl experimental describe service

    Analyzes service, pods, DestinationRules, and VirtualServices and reports the configuration objects that affect that service.

    THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental describe service <svc> [flags]
    1. istioctl experimental describe svc <svc> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--ignoreUnmeshed</code></td><td></td><td>Suppress warnings for unmeshed pods</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl experimental describe service productpage

    istioctl experimental kube-uninject

    kube-uninject is used to prevent Istio from adding a sidecar and also provides the inverse of “istioctl kube-inject -f”.

    1. istioctl experimental kube-uninject [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>Input Kubernetes resource filename (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oModified output Kubernetes resource filename (default ``)

    Examples

    1. # Update resources before applying.
    2. kubectl apply -f <(istioctl experimental kube-uninject -f <resource.yaml>)
    3. # Create a persistent version of the deployment by removing Envoy sidecar.
    4. istioctl experimental kube-uninject -f deployment.yaml -o deployment-uninjected.yaml
    5. # Update an existing deployment.
    6. kubectl get deployment -o yaml | istioctl experimental kube-uninject -f - | kubectl apply -f -

    istioctl experimental metrics

    Prints the metrics for the specified service(s) when running in Kubernetes.

    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.

    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.

    1. istioctl experimental metrics <workload name>...
    1. istioctl experimental m <workload name>...
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. # Retrieve workload metrics for productpage-v1 workload
    2. istioctl experimental metrics productpage-v1
    3. # Retrieve workload metrics for various services in the different namespaces
    4. istioctl experimental metrics productpage-v1.foo reviews-v1.bar ratings-v1.baz

    istioctl experimental multicluster

    Commands to assist in managing a multi-cluster mesh

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental multicluster apply

    Update clusters in a multi-cluster mesh based on mesh topology

    1. istioctl experimental multicluster apply -f <mesh.yaml> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>filename of the multicluster mesh description (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)

    istioctl experimental multicluster describe

    Describe status of the multi-cluster mesh’s control plane’

    1. istioctl experimental multicluster describe -f <mesh.yaml> [--all] [flags]
    FlagsShorthandDescription
    —alldescribe the status of all clustersByContext in the mesh
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>filename of the multicluster mesh description (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)

    istioctl experimental multicluster generate

    generate a cluster-specific control plane configuration based on the mesh description and runtime state

    1. istioctl experimental multicluster generate -f <mesh.yaml> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>filename of the multicluster mesh description (default)
    —from <string>optional source configuration to generate multicluster aware configuration from (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default )
    —namespace <string>-nConfig namespace (default ``)
    —wait-for-gatewayswait for all cluster’s istio-ingressgateway IPs to be ready before generating configuration.

    istioctl experimental post-install

    Commands related to post-install

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental post-install webhook

    webhook command to manage webhook configurations

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental post-install webhook disable

    Disable webhook configurations

    1. istioctl experimental post-install webhook disable [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--injection</code></td><td></td><td>Disable mutating webhook (default true).</td></tr><tr><td><code>--injection-config &lt;string&gt;</code></td><td></td><td>The mutating webhook configuration to disable. (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--validation</code></td><td></td><td>Disable validating webhook (default true).</td></tr><tr><td><code>--validation-config &lt;string&gt;</code></td><td></td><td>The validating webhook configuration to disable. (defaultistio-galley`)

    Examples

    1. # Disable all webhooks
    2. istioctl experimental post-install webhook disable
    3. # Disable all webhooks except injection
    4. istioctl experimental post-install webhook disable --injection=false

    istioctl experimental post-install webhook enable

    This command is used to enable webhook configurations after installing Istio. For previous Istio versions (e.g., 1.2, 1.3, etc), this command is not needed because in previous versions webhooks manage their own configurations.

    1. istioctl experimental post-install webhook enable [flags]
    FlagsShorthandDescription
    —ca-bundle-file <string>PEM encoded CA bundle which will be used to validate the webhook’s server certificates. If this is empty, the kube-apisever’s root CA is used if it can be confirmed to have signed the webhook’s certificates. This condition is sometimes true but is not guaranteed (see https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping) (default )</td></tr><tr><td><code>--context &lt;string&gt;</code></td><td></td><td>The name of the kubeconfig context to use (default)
    —injectionEnable injection webhook (default true).
    —injection-path <string>The file path of the injection webhook configuration. (default )</td></tr><tr><td><code>--injection-service &lt;string&gt;</code></td><td></td><td>The service name of the injection webhook to manage. (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--read-cert-timeout &lt;duration&gt;</code></td><td></td><td>Max time for waiting the webhook certificate to be readable. (default `1m0s`)</td></tr><tr><td><code>--timeout &lt;duration&gt;</code></td><td></td><td>Max time for checking the validating webhook server. If the validating webhook server is not readyin the given time, exit. Otherwise, apply the webhook configuration. (default `1m0s`)</td></tr><tr><td><code>--validation</code></td><td></td><td>Enable validatation webhook (default true).</td></tr><tr><td><code>--validation-path &lt;string&gt;</code></td><td></td><td>The file path of the validation webhook configuration. (default)
    —validation-service <string>The service name of the validation webhook to manage. (default istio-galley)
    —webhook-secret <string>The name of an existing Kubernetes secret of a webhook. istioctl will verify that the webhook certificate is issued by the CA certificate. (default ``)

    Examples

    1. # Enable the webhook configuration of Galley with the given webhook configuration
    2. istioctl experimental post-install webhook enable --validation --webhook-secret istio.webhook.galley
    3. --namespace istio-system --validation-path validatingwebhookconfiguration.yaml
    4. # Enable the webhook configuration of Galley with the given webhook configuration and CA certificate
    5. istioctl experimental post-install webhook enable --validation --webhook-secret istio.webhook.galley
    6. --namespace istio-system --validation-path validatingwebhookconfiguration.yaml --ca-bundle-file ./k8s-ca-cert.pem

    istioctl experimental post-install webhook status

    Get webhook configurations

    1. istioctl experimental post-install webhook status [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--injection</code></td><td></td><td>Display the injection webhook configuration.</td></tr><tr><td><code>--injection-config &lt;string&gt;</code></td><td></td><td>The name of the MutatingWebhookConfiguration to display. (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--validation</code></td><td></td><td>Display the validating webhook configuration.</td></tr><tr><td><code>--validation-config &lt;string&gt;</code></td><td></td><td>The name of the ValidatingWebhookConfiguration to display. (defaultistio-galley`)

    Examples

    1. # Display the webhook configuration of Galley
    2. istioctl experimental post-install webhook status --validation --validation-config istio-galley
    3. # Display the webhook configuration of Galley and Sidecar Injector
    4. istioctl experimental post-install webhook status --validation --validation-config istio-galley
    5. --injection --injection-config istio-sidecar-injector

    istioctl experimental remove-from-mesh

    Remove workloads from Istio service mesh

    1. istioctl experimental remove-from-mesh [flags]
    1. istioctl experimental rm [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    istioctl experimental remove-from-mesh external-service

    istioctl experimental remove-from-mesh external-service remove the ServiceEntry and\ the kubernetes Service for the specified external service(eg:services running on VM) from Istio service mesh. The typical usage scenario is Mesh Expansion on VMs. THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental remove-from-mesh external-service <svcname> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)
    1. istioctl experimental remove-from-mesh external-service vmhttp

    istioctl experimental remove-from-mesh service

    istioctl experimental remove-from-mesh service restarts pods with the Istio sidecar un-injected. THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    1. istioctl experimental remove-from-mesh service [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)

    Examples

    1. istioctl experimental remove-from-mesh service productpage

    istioctl experimental upgrade

    The upgrade command checks for upgrade version eligibility and, if eligible, upgrades the Istio control plane components in-place. Warning: traffic may be disrupted during upgrade. Please ensure PodDisruptionBudgets are defined to maintain service continuity.

    1. istioctl experimental upgrade [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>Path to file containing IstioControlPlane CustomResource (default)
    —forceApply the upgrade without eligibility checks and testing for changes in profile default values
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--logtostderr</code></td><td></td><td>Send logs to stderr.</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —skip-confirmationIf skip-confirmation is set, skips the prompting confirmation for value changes in this upgrade
    —verboseVerbose output.
    —versionsURI <string>-uURI for operator versions to Istio versions map (default https://raw.githubusercontent.com/istio/operator/master/data/versions.yaml)
    —wait-wWait, if set will wait until all Pods, Services, and minimum number of Pods of a Deployment are in a ready state before the command exits. It will wait for a maximum duration of 10m0s

    istioctl experimental wait

    1. istioctl experimental wait [flags] <type> <name>[.<namespace>]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--for &lt;string&gt;</code></td><td></td><td>wait condition, must be 'distribution' or 'delete' (default `distribution`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--resource-version &lt;string&gt;</code></td><td></td><td>wait for a specific version of config to become current, rather than using whatever is latest in kubernetes (default)
    —threshold <float32>the ratio of distribution required for success (default 1)
    —timeout <duration>the duration to wait before failing (default 30s)

    Examples

    1. # Wait until the bookinfo virtual service has been distributed to all proxies in the mesh
    2. istioctl experimental wait --for=distribution virtualservice bookinfo.default
    3. # Wait until 99% of the proxies receive the distribution, timing out after 5 minutes
    4. istioctl experimental wait --for=distribution --threshold=.99 --timeout=300 virtualservice bookinfo.default

    istioctl kube-inject

    kube-inject manually injects the Envoy sidecar into Kubernetes workloads. Unsupported resources are left unmodified so it is safe to run kube-inject over a single file that contains multiple Service, ConfigMap, Deployment, etc. definitions for a complex application. It’s best to do this when the resource is initially created.

    k8s.io/docs/concepts/workloads/pods/pod-overview/#pod-templates is updated for Job, DaemonSet, ReplicaSet, Pod and Deployment YAML resource documents. Support for additional pod-based resource types can be added as necessary.

    The Istio project is continually evolving so the Istio sidecar configuration may change unannounced. When in doubt re-run istioctl kube-inject on deployments to get the most up-to-date changes.

    1. istioctl kube-inject [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>Input Kubernetes resource filename (default)
    —injectConfigFile <string>injection configuration filename. Cannot be used with —injectConfigMapName (default )</td></tr><tr><td><code>--injectConfigMapName &lt;string&gt;</code></td><td></td><td>ConfigMap name for Istio sidecar injection, key should be "config". (default `istio-sidecar-injector`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —meshConfigFile <string>mesh configuration filename. Takes precedence over —meshConfigMapName if set (default )</td></tr><tr><td><code>--meshConfigMapName &lt;string&gt;</code></td><td></td><td>ConfigMap name for Istio mesh configuration, key should be "mesh" (default `istio`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oModified output Kubernetes resource filename (default )</td></tr><tr><td><code>--valuesFile &lt;string&gt;</code></td><td></td><td>injection values configuration filename. (default)

    Examples

    1. # Update resources on the fly before applying.
    2. kubectl apply -f <(istioctl kube-inject -f <resource.yaml>)
    3. # Create a persistent version of the deployment with Envoy sidecar
    4. # injected.
    5. istioctl kube-inject -f deployment.yaml -o deployment-injected.yaml
    6. kubectl get deployment -o yaml | istioctl kube-inject -f - | kubectl apply -f -
    7. # Capture cluster configuration for later use with kube-inject
    8. kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.config}" > /tmp/inj-template.tmpl
    9. kubectl -n istio-system get cm istio -o jsonpath="{.data.mesh}" > /tmp/mesh.yaml
    10. kubectl -n istio-system get cm istio-sidecar-injector -o jsonpath="{.data.values}" > /tmp/values.json
    11. # Use kube-inject based on captured configuration
    12. istioctl kube-inject -f samples/bookinfo/platform/kube/bookinfo.yaml \
    13. --injectConfigFile /tmp/inj-template.tmpl \
    14. --meshConfigFile /tmp/mesh.yaml \
    15. --valuesFile /tmp/values.json

    istioctl manifest

    The manifest subcommand generates, applies, diffs or migrates Istio manifests.

    The apply subcommand generates an Istio install manifest and applies it to a cluster.

    1. istioctl manifest apply [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>Path to file containing IstioControlPlane CustomResource (default)
    —forceProceed even with validation errors
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--logtostderr</code></td><td></td><td>Send logs to stderr.</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —readiness-timeout <duration>Maximum seconds to wait for all Istio resources to be ready. The —wait flag must be set for this flag to apply (default 5m0s)
    —set <stringSlice>-sSet a value in IstioControlPlane CustomResource. e.g. —set policy.enabled=true. Overrides the corresponding path value in the selected profile or passed through IstioControlPlane CR customization file (default [])
    —skip-confirmationskipConfirmation 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.
    —verboseVerbose output.
    —wait-wWait, if set will wait until all Pods, Services, and minimum number of Pods of a Deployment are in a ready state before the command exits. It will wait for a maximum duration of —readiness-timeout seconds

    istioctl manifest diff

    The diff subcommand compares manifests from two files or directories.

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--directory</code></td><td><code>-r</code></td><td>compare directory</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--ignore &lt;string&gt;</code></td><td></td><td>ignoreResources ignores all listed items during comparison. It uses the same list format as selectResources (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--logtostderr</code></td><td></td><td>Send logs to stderr.</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —rename <string>renameResources identifies renamed resources before comparison. The format of each renaming pair is A->B, all renaming pairs are comma separated. e.g. Service::istio-pilot->Service::istio-control - rename istio-pilot service into istio-control (default `)</td></tr><tr><td><code>--select &lt;string&gt;</code></td><td></td><td>selectResources constrains 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:*:istio-pilot - compare Services called "istio-pilot" in all namespaces (default::`)
    —verboseVerbose output.

    istioctl manifest generate

    The generate subcommand generates an Istio install manifest and outputs to the console by default.

    1. istioctl manifest generate [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--filename &lt;string&gt;</code></td><td><code>-f</code></td><td>Path to file containing IstioControlPlane CustomResource (default)
    —forceProceed even with validation errors
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--logtostderr</code></td><td></td><td>Send logs to stderr.</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oManifest output directory path (default `)</td></tr><tr><td><code>--set &lt;stringSlice&gt;</code></td><td><code>-s</code></td><td>Set a value in IstioControlPlane CustomResource. e.g. --set policy.enabled=true. Overrides the corresponding path value in the selected profile or passed through IstioControlPlane CR customization file (default[]`)
    —verboseVerbose output.

    istioctl manifest migrate

    The migrate subcommand migrates a configuration from Helm values format to IstioControlPlane format.

    1. istioctl manifest migrate [<filepath>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default ``)
    —verboseVerbose output.

    istioctl manifest versions

    List the versions of Istio recommended for use or supported for upgrade by this version of the operator binary.

    1. istioctl manifest versions [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--verbose</code></td><td></td><td>Verbose output.</td></tr><tr><td><code>--versionsURI &lt;string&gt;</code></td><td><code>-u</code></td><td>URI for operator versions to Istio versions map (defaulthttps://raw.githubusercontent.com/istio/operator/master/data/versions.yaml`)

    istioctl profile

    The profile subcommand lists, dumps or diffs Istio configuration profiles.

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default ``)
    —verboseVerbose output.

    istioctl profile diff

    The diff subcommand displays the differences between two Istio configuration profiles.

    1. istioctl profile diff <file1.yaml> <file2.yaml> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default ``)
    —verboseVerbose output.

    istioctl profile dump

    The dump subcommand dumps the values in an Istio configuration profile.

    1. istioctl profile dump [<profile>] [flags]
    FlagsShorthandDescription
    —config-path <string>-pThe path the root of the configuration subtree to dump e.g. trafficManagement.components.pilot. By default, dump whole tree (default )</td></tr><tr><td><code>--context &lt;string&gt;</code></td><td></td><td>The name of the kubeconfig context to use (default)
    —dry-runConsole/log output only, make no changes.
    —filename <string>-fPath to file containing IstioControlPlane CustomResource (default )</td></tr><tr><td><code>--helm-values</code></td><td></td><td>If set, dumps the Helm values that IstioControlPlaceSpec is translated to before manifests are rendered</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default ``)
    —verboseVerbose output.

    istioctl profile list

    The list subcommand lists the available Istio configuration profiles.

    1. istioctl profile list [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--dry-run</code></td><td></td><td>Console/log output only, make no changes.</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —logtostderrSend logs to stderr.
    —namespace <string>-nConfig namespace (default ``)
    —verboseVerbose output.

    istioctl proxy-config

    A group of commands used to retrieve information about proxy configuration from the Envoy config dump

    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--output &lt;string&gt;</code></td><td><code>-o</code></td><td>Output format: one of json|short (defaultshort`)

    Examples

    1. # Retrieve information about proxy configuration from an Envoy instance.
    2. istioctl proxy-config <clusters|listeners|routes|endpoints|bootstrap> <pod-name[.namespace]>

    istioctl proxy-config bootstrap

    Retrieve information about bootstrap configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config bootstrap [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config b [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;string&gt;</code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of json|short (default short)

    Examples

    1. # Retrieve full bootstrap configuration for a given pod from Envoy.
    2. istioctl proxy-config bootstrap <pod-name[.namespace]>
    3. # Retrieve full bootstrap without using Kubernetes API
    4. ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
    5. istioctl proxy-config bootstrap --file envoy-config.json

    istioctl proxy-config cluster

    Retrieve information about cluster configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config cluster [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config clusters [<pod-name[.namespace]>] [flags]
    2. istioctl proxy-config c [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--direction &lt;string&gt;</code></td><td></td><td>Filter clusters by Direction field (default)
    —file <string>-fEnvoy config dump JSON file (default )</td></tr><tr><td><code>--fqdn &lt;string&gt;</code></td><td></td><td>Filter clusters by substring of Service FQDN field (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of json|short (default short)
    —port <int>Filter clusters by Port field (default 0)
    —subset <string>Filter clusters by substring of Subset field (default ``)

    Examples

    1. # Retrieve summary about cluster configuration for a given pod from Envoy.
    2. istioctl proxy-config clusters <pod-name[.namespace]>
    3. # Retrieve cluster summary for clusters with port 9080.
    4. istioctl proxy-config clusters <pod-name[.namespace]> --port 9080
    5. # Retrieve full cluster dump for clusters that are inbound with a FQDN of details.default.svc.cluster.local.
    6. istioctl proxy-config clusters <pod-name[.namespace]> --fqdn details.default.svc.cluster.local --direction inbound -o json
    7. # Retrieve cluster summary without using Kubernetes API
    8. ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
    9. istioctl proxy-config clusters --file envoy-config.json

    istioctl proxy-config endpoint

    Retrieve information about endpoint configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config endpoint [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config endpoints [<pod-name[.namespace]>] [flags]
    2. istioctl proxy-config ep [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —address <string>Filter endpoints by address field (default )</td></tr><tr><td><code>--cluster &lt;string&gt;</code></td><td></td><td>Filter endpoints by cluster name field (default)
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;string&gt;</code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of json|short (default short)
    —port <int>Filter endpoints by Port field (default 0)
    —status <string>Filter endpoints by status field (default ``)

    Examples

    1. # Retrieve full endpoint configuration for a given pod from Envoy.
    2. istioctl proxy-config endpoint <pod-name[.namespace]>
    3. # Retrieve endpoint summary for endpoint with port 9080.
    4. istioctl proxy-config endpoint <pod-name[.namespace]> --port 9080
    5. # Retrieve full endpoint with a address (172.17.0.2).
    6. istioctl proxy-config endpoint <pod-name[.namespace]> --address 172.17.0.2 -o json
    7. # Retrieve full endpoint with a cluster name (outbound|9411||zipkin.istio-system.svc.cluster.local).
    8. istioctl proxy-config endpoint <pod-name[.namespace]> --cluster "outbound|9411||zipkin.istio-system.svc.cluster.local" -o json
    9. # Retrieve full endpoint with the status (healthy).
    10. istioctl proxy-config endpoint <pod-name[.namespace]> --status healthy -ojson
    11. # Retrieve endpoint summary without using Kubernetes API
    12. ssh <user@hostname> 'curl localhost:15000/clusters?format=json' > envoy-clusters.json
    13. istioctl proxy-config endpoints --file envoy-clusters.json

    istioctl proxy-config listener

    Retrieve information about listener configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config listener [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config listeners [<pod-name[.namespace]>] [flags]
    2. istioctl proxy-config l [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —address <string>Filter listeners by address field (default )</td></tr><tr><td><code>--context &lt;string&gt;</code></td><td></td><td>The name of the kubeconfig context to use (default)
    —file <string>-fEnvoy config dump JSON file (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--output &lt;string&gt;</code></td><td><code>-o</code></td><td>Output format: one of json|short (default `short`)</td></tr><tr><td><code>--port &lt;int&gt;</code></td><td></td><td>Filter listeners by Port field (default `0`)</td></tr><tr><td><code>--type &lt;string&gt;</code></td><td></td><td>Filter listeners by type field (default)

    Examples

    1. # Retrieve summary about listener configuration for a given pod from Envoy.
    2. istioctl proxy-config listeners <pod-name[.namespace]>
    3. # Retrieve listener summary for listeners with port 9080.
    4. istioctl proxy-config listeners <pod-name[.namespace]> --port 9080
    5. # Retrieve full listener dump for HTTP listeners with a wildcard address (0.0.0.0).
    6. istioctl proxy-config listeners <pod-name[.namespace]> --type HTTP --address 0.0.0.0 -o json
    7. # Retrieve listener summary without using Kubernetes API
    8. ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
    9. istioctl proxy-config listeners --file envoy-config.json

    istioctl proxy-config log

    (experimental) Retrieve information about logging levels of the Envoy instance in the specified pod, and update optionally

    1. istioctl proxy-config log <pod-name[.namespace]> [flags]
    1. istioctl proxy-config o <pod-name[.namespace]> [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —level <string>Comma-separated minimum per-logger level of messages to output, in the form of [<logger>:]<level>,[<logger>:]<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>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of json|short (default short)
    —reset-rReset levels to default value (warning).

    Examples

    1. # Retrieve information about logging levels for a given pod from Envoy.
    2. istioctl proxy-config log <pod-name[.namespace]>
    3. # Update levels of the all loggers
    4. istioctl proxy-config log <pod-name[.namespace]> --level none
    5. # Update levels of the specified loggers.
    6. istioctl proxy-config log <pod-name[.namespace]> --level http:debug,redis:debug
    7. # Reset levels of all the loggers to default value (warning).

    istioctl proxy-config route

    Retrieve information about route configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config route [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config routes [<pod-name[.namespace]>] [flags]
    2. istioctl proxy-config r [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;string&gt;</code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--name &lt;string&gt;</code></td><td></td><td>Filter listeners by route name field (default)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--output &lt;string&gt;</code></td><td><code>-o</code></td><td>Output format: one of json|short (defaultshort`)

    Examples

    1. # Retrieve summary about route configuration for a given pod from Envoy.
    2. istioctl proxy-config routes <pod-name[.namespace]>
    3. # Retrieve route summary for route 9080.
    4. istioctl proxy-config route <pod-name[.namespace]> --name 9080
    5. # Retrieve full route dump for route 9080
    6. istioctl proxy-config route <pod-name[.namespace]> --name 9080 -o json
    7. # Retrieve route summary without using Kubernetes API
    8. ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
    9. istioctl proxy-config routes --file envoy-config.json

    istioctl proxy-config secret

    (experimental) Retrieve information about secret configuration for the Envoy instance in the specified pod.

    1. istioctl proxy-config secret [<pod-name[.namespace]>] [flags]
    1. istioctl proxy-config s [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--file &lt;string&gt;</code></td><td><code>-f</code></td><td>Envoy config dump JSON file (default)
    —istioNamespace <string>-iIstio system namespace (default istio-system)
    —kubeconfig <string>-cKubernetes configuration file (default )</td></tr><tr><td><code>--log_output_level &lt;string&gt;</code></td><td></td><td>Comma-separated minimum per-scope logging level of messages to output, in the form of &lt;scope&gt;:&lt;level&gt;,&lt;scope&gt;:&lt;level&gt;,... where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default `default:info,validation:error,processing:error,source:error,analysis:warn`)</td></tr><tr><td><code>--namespace &lt;string&gt;</code></td><td><code>-n</code></td><td>Config namespace (default)
    —output <string>-oOutput format: one of json|short (default short)

    Examples

    1. # Retrieve full secret configuration for a given pod from Envoy.
    2. istioctl proxy-config secret <pod-name[.namespace]>
    3. # Retrieve full bootstrap without using Kubernetes API
    4. ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
    5. istioctl proxy-config secret --file envoy-config.json
    6. THIS COMMAND IS STILL UNDER ACTIVE DEVELOPMENT AND NOT READY FOR PRODUCTION USE.

    istioctl proxy-status

    Retrieves last sent and last acknowledged xDS sync from Pilot to each Envoy in the mesh

    1. istioctl proxy-status [<pod-name[.namespace]>] [flags]
    1. istioctl ps [<pod-name[.namespace]>] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)
    —sds-s(experimental) Retrieve synchronization between active secrets on Envoy instance with those on corresponding node agents
    —sds-jsonDetermines whether SDS dump outputs JSON

    Examples

    1. # Retrieve sync status for all Envoys in a mesh
    2. istioctl proxy-status
    3. # Retrieve sync diff for a single Envoy and Pilot
    4. istioctl proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system

    istioctl register

    Registers a service instance (e.g. VM) joining the mesh

    1. istioctl register <svcname> <ip> [name1:]port1 [name2:]port2 ... [flags]
    FlagsShorthandDescription
    —annotations <stringSlice>-aList of string annotations to apply if creating a service/endpoint; e.g. -a foo=bar,test,x=y (default [])
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —labels <stringSlice>-lList of labels to apply if creating a service/endpoint; e.g. -l env=prod,vers=2 (default [])
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default `)</td></tr><tr><td><code>--serviceaccount &lt;string&gt;</code></td><td><code>-s</code></td><td>Service account to link to the service (defaultdefault`)

    istioctl validate

    Validate Istio policy and rules (NOTE: validate is deprecated and will be removed in 1.6. Use ‘istioctl analyze’ to validate configuration.)

    1. istioctl validate -f FILENAME [options] [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--filename &lt;stringSlice&gt;</code></td><td><code>-f</code></td><td>Names of files to validate (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)
    —referential-xEnable structural validation for policy and telemetry
    1. # Validate bookinfo-gateway.yaml
    2. istioctl validate -f bookinfo-gateway.yaml
    3. # Validate current deployments under 'default' namespace within the cluster
    4. kubectl get deployments -o yaml |istioctl validate -f -
    5. # Validate current services under 'default' namespace within the cluster
    6. kubectl get services -o yaml |istioctl validate -f -
    7. # Also see the related command 'istioctl analyze'
    8. istioctl analyze samples/bookinfo/networking/bookinfo-gateway.yaml

    istioctl verify-install

    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.

    If you do not specify installation file it will perform pre-check for your cluster and report whether the cluster is ready for Istio installation.

    1. istioctl verify-install [flags]
    FlagsShorthandDescription
    —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--enableVerbose</code></td><td></td><td>Enable verbose output</td></tr><tr><td><code>--filename &lt;stringSlice&gt;</code></td><td><code>-f</code></td><td>Istio YAML installation file. (default `[]`)</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
    —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
    —namespace <string>-nConfig namespace (default ``)
    —recursive-RProcess the directory used in -f, —filename recursively. Useful when you want to manage related manifests organized within the same directory.

    Examples

    1. # Verify that Istio can be freshly installed
    2. istioctl verify-install
    3. # Verify the deployment matches a custom Istio deployment configuration
    4. istioctl verify-install -f $HOME/istio.yaml

    istioctl version

      FlagsShorthandDescription
      —context <string>The name of the kubeconfig context to use (default )</td></tr><tr><td><code>--istioNamespace &lt;string&gt;</code></td><td><code>-i</code></td><td>Istio system namespace (default `istio-system`)</td></tr><tr><td><code>--kubeconfig &lt;string&gt;</code></td><td><code>-c</code></td><td>Kubernetes configuration file (default)
      —log_output_level <string>Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>,… where scope can be one of [ads, all, analysis, attributes, authn, cacheLog, citadelClientLog, configMapController, conversions, default, googleCAClientLog, grpcAdapter, kube, kube-converter, mcp, meshconfig, model, patch, processing, rbac, resource, runtime, sdsServiceLog, secretFetcherLog, source, stsClientLog, tpath, translator, util, validation, vaultClientLog] and level can be one of [debug, info, warn, error, fatal, none] (default default:info,validation:error,processing:error,source:error,analysis:warn)
      —namespace <string>-nConfig namespace (default )</td></tr><tr><td><code>--output &lt;string&gt;</code></td><td><code>-o</code></td><td>One of 'yaml' or 'json'. (default)
      —remoteUse —remote=false to suppress control plane check
      —short-sUse —short=false to generate full version information

      Environment variables

      These environment variables affect the behavior of the istioctl command.

      Metric NameTypeDescription
      endpoint_no_podLastValueEndpoints without an associated pod.
      galley_runtime_processor_event_span_duration_millisecondsDistributionThe duration between each incoming event
      galley_runtime_processor_events_processed_totalCountThe number of events that have been processed
      galley_runtime_processor_snapshot_events_totalDistributionThe number of events per snapshot
      galley_runtime_processor_snapshot_lifetime_duration_millisecondsDistributionThe duration of each snapshot
      galley_runtime_processor_snapshots_published_totalCountThe number of snapshots that have been published
      galley_runtime_state_type_instances_totalLastValueThe number of type instances per type URL
      galley_runtime_strategy_on_change_totalCountThe number of times the strategy’s onChange has been called
      galley_runtime_strategy_timer_max_time_reached_totalCountThe number of times the max time has been reached
      galley_runtime_strategy_timer_quiesce_reached_totalCountThe number of times a quiesce has been reached
      galley_runtime_strategy_timer_resets_totalCountThe number of times the timer has been reset
      galley_source_kube_dynamic_converter_failure_totalCountThe number of times a dynamnic kubernetes source failed converting a resources
      galley_source_kube_dynamic_converter_success_totalCountThe number of times a dynamic kubernetes source successfully converted a resource
      galley_source_kube_event_error_totalCountThe number of times a kubernetes source encountered errored while handling an event
      galley_source_kube_event_success_totalCountThe number of times a kubernetes source successfully handled an event
      istio_buildLastValueIstio component build info
      istio_mcp_clients_totalLastValueThe number of streams currently connected.
      istio_mcp_message_sizes_bytesDistributionSize of messages received from clients.
      istio_mcp_reconnectionsSumThe number of times the sink has reconnected.
      istio_mcp_recv_failures_totalSumThe number of recv failures in the source.
      istio_mcp_request_acks_totalSumThe number of request acks received by the source.
      istio_mcp_request_nacks_totalSumThe number of request nacks received by the source.
      istio_mcp_send_failures_totalSumThe number of send failures in the source.
      mixer_config_adapter_info_config_errors_totalLastValueThe number of errors encountered during processing of the adapter info configuration.
      mixer_config_adapter_info_configs_totalLastValueThe number of known adapters in the current config.
      mixer_config_attributes_totalLastValueThe number of known attributes in the current config.
      mixer_config_handler_configs_totalLastValueThe number of known handlers in the current config.
      mixer_config_handler_validation_error_totalLastValueThe number of errors encountered because handler validation returned error.
      mixer_config_instance_config_errors_totalLastValueThe number of errors encountered during processing of the instance configuration.
      mixer_config_instance_configs_totalLastValueThe number of known instances in the current config.
      mixer_config_rule_config_errors_totalLastValueThe number of errors encountered during processing of the rule configuration.
      mixer_config_rule_config_match_error_totalLastValueThe number of rule conditions that was not parseable.
      mixer_config_rule_configs_totalLastValueThe number of known rules in the current config.
      mixer_config_template_config_errors_totalLastValueThe number of errors encountered during processing of the template configuration.
      mixer_config_template_configs_totalLastValueThe number of known templates in the current config.
      mixer_config_unsatisfied_action_handler_totalLastValueThe number of actions that failed due to handlers being unavailable.
      mixer_dispatcher_destinations_per_requestDistributionNumber of handlers dispatched per request by Mixer
      mixer_dispatcher_destinations_per_variety_totalLastValueNumber of Mixer adapter destinations by template variety type
      mixer_dispatcher_instances_per_requestDistributionNumber of instances created per request by Mixer
      mixer_handler_closed_handlers_totalLastValueThe number of handlers that were closed during config transition.
      mixer_handler_daemons_totalLastValueThe current number of active daemon routines in a given adapter environment.
      mixer_handler_handler_build_failures_totalLastValueThe number of handlers that failed creation during config transition.
      mixer_handler_handler_close_failures_totalLastValueThe number of errors encountered while closing handlers during config transition.
      mixer_handler_new_handlers_totalLastValueThe number of handlers that were newly created during config transition.
      mixer_handler_reused_handlers_totalLastValueThe number of handlers that were re-used during config transition.
      mixer_handler_workers_totalLastValueThe current number of active worker routines in a given adapter environment.
      mixer_runtime_dispatch_duration_secondsDistributionDuration in seconds for adapter dispatches handled by Mixer.
      mixer_runtime_dispatches_totalCountTotal number of adapter dispatches handled by Mixer.
      num_failed_outgoing_requestsSumNumber of failed outgoing requests (e.g. to a token exchange server, CA, etc.)
      num_outgoing_requestsSumNumber of total outgoing requests (e.g. to a token exchange server, CA, etc.)
      num_outgoing_retriesSumNumber of outgoing retry requests (e.g. to a token exchange server, CA, etc.)
      outgoing_latencySumThe latency of outgoing requests (e.g. to a token exchange server, CA, etc.) in milliseconds.
      pilot_conflict_inbound_listenerLastValueNumber of conflicting inbound listeners.
      pilot_conflict_outbound_listener_http_over_current_tcpLastValueNumber of conflicting wildcard http listeners with current wildcard tcp listener.
      pilot_conflict_outbound_listener_http_over_httpsLastValueNumber of conflicting HTTP listeners with well known HTTPS ports
      pilot_conflict_outbound_listener_tcp_over_current_httpLastValueNumber of conflicting wildcard tcp listeners with current wildcard http listener.
      pilot_conflict_outbound_listener_tcp_over_current_tcpLastValueNumber of conflicting tcp listeners with current tcp listener.
      pilot_destrule_subsetsLastValueDuplicate subsets across destination rules for same host
      pilot_duplicate_envoy_clustersLastValueDuplicate envoy clusters caused by service entries with same hostname
      pilot_eds_no_instancesLastValueNumber of clusters without instances.
      pilot_endpoint_not_readyLastValueEndpoint found in unready state.
      pilot_inbound_updatesSumTotal number of updates received by pilot.
      pilot_invalid_out_listenersLastValueNumber of invalid outbound listeners.
      pilot_jwks_resolver_network_fetch_fail_totalSumTotal number of failed network fetch by pilot jwks resolver
      pilot_jwks_resolver_network_fetch_success_totalSumTotal number of successfully network fetch by pilot jwks resolver
      pilot_k8s_cfg_eventsSumEvents from k8s config.
      pilot_k8s_endpoints_with_no_podsSumEndpoints that does not have any corresponding pods.
      pilot_k8s_object_errorsLastValueErrors converting k8s CRDs
      pilot_k8s_reg_eventsSumEvents from k8s registry.
      pilot_no_ipLastValuePods not found in the endpoint table, possibly invalid.
      pilot_proxy_convergence_timeDistributionDelay in seconds between config change and a proxy receiving all required configuration.
      pilot_proxy_queue_timeDistributionTime in seconds, a proxy is in the push queue before being dequeued.
      pilot_rds_expired_nonceSumTotal number of RDS messages with an expired nonce.
      pilot_servicesLastValueTotal services known to pilot.
      pilot_total_rejected_configsSumTotal number of configs that Pilot had to reject or ignore.
      pilot_total_xds_internal_errorsSumTotal number of internal XDS errors in pilot.
      pilot_total_xds_rejectsSumTotal number of XDS responses from pilot rejected by proxy.
      pilot_virt_servicesLastValueTotal virtual services known to pilot.
      pilot_vservice_dup_domainLastValueVirtual services with dup domains.
      pilot_xdsLastValueNumber of endpoints connected to this pilot using XDS.
      pilot_xds_cds_rejectLastValuePilot rejected CDS configs.
      pilot_xds_eds_all_locality_endpointsLastValueNetwork endpoints for each cluster(across all localities), as of last push. Zero endpoints is an error.
      pilot_xds_eds_instancesLastValueInstances for each cluster(grouped by locality), as of last push. Zero instances is an error.
      pilot_xds_eds_rejectLastValuePilot rejected EDS.
      pilot_xds_lds_rejectLastValuePilot rejected LDS.
      pilot_xds_push_context_errorsSumNumber of errors (timeouts) initiating push context.
      pilot_xds_push_timeDistributionTotal time in seconds Pilot takes to push lds, rds, cds and eds.
      pilot_xds_pushesSumPilot build and send errors for lds, rds, cds and eds.
      pilot_xds_rds_rejectLastValuePilot rejected RDS.
      pilot_xds_write_timeoutSumPilot XDS response write timeouts.
      sidecar_injection_failure_totalSumTotal number of failed Side car injection requests.
      sidecar_injection_requests_totalSumTotal number of Side car injection requests.
      sidecar_injection_skip_totalSumTotal number of skipped injection requests.
      sidecar_injection_success_totalSumTotal number of successful Side car injection requests.
      total_active_connectionsSumThe total number of active SDS connections.
      total_push_errorsSumThe total number of failed SDS pushes.
      total_pushesSumThe total number of SDS pushes.
      total_secret_update_failuresSumThe total number of dynamic secret update failures reported by proxy.
      total_stale_connectionsThe total number of stale SDS connections.