istioctl

A group of commands used to manage istiod configuration

istioctl istiod [flags]

  # Retrieve information about istiod configuration.
  istioctl admin log

istioctl admin log

Retrieve or update logging levels of istiod components.

istioctl admin log [<pod-name>] [--level <scope>:<level>][--stack-trace-level <scope>:<level>]|[-r|--reset]|[--output|-o short|yaml] [flags]

istioctl admin l [<pod-name>] [--level <scope>:<level>][--stack-trace-level <scope>:<level>]|[-r|--reset]|[--output|-o short|yaml] [flags]

Examples

  # Retrieve information about istiod logging levels.
  istioctl admin log
  # Retrieve information about istiod logging levels on a specific control plane pod.
  istioctl admin l istiod-5c868d8bdd-pmvgg
  # Update levels of the specified loggers.
  istioctl admin log --level ads:debug,authorization:debug
  # Reset levels of all the loggers to default value (info).
  istioctl admin log -r

istioctl analyze

Analyze Istio configuration and print validation messages

istioctl analyze <file>... [flags]

Examples

  # Analyze the current live cluster
  istioctl analyze
  # Analyze the current live cluster, simulating the effect of applying additional yaml files
  istioctl analyze a.yaml b.yaml my-app-config/
  # Analyze the current live cluster, simulating the effect of applying a directory of config recursively
  istioctl analyze --recursive my-istio-config/
  # Analyze yaml files without connecting to a live cluster
  istioctl analyze --use-kube=false a.yaml b.yaml my-app-config/
  # Analyze the current live cluster and suppress PodMissingProxy for pod mypod in namespace 'testing'.
  istioctl analyze -S "IST0103=Pod mypod.testing"
  # Analyze the current live cluster and suppress PodMissingProxy for all pods in namespace 'testing',
  # and suppress MisplacedAnnotation on deployment foobar in namespace default.
  istioctl analyze -S "IST0103=Pod *.testing" -S "IST0107=Deployment foobar.default"
  # List available analyzers
  istioctl analyze -L

istioctl authz

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

istioctl authz [flags]

istioctl bug-report

bug-report selectively captures cluster information and logs into an archive to help diagnose problems. Proxy logs can be filtered using: —include|—exclude ns1,ns2…/dep1,dep2…/pod1,pod2…/cntr1,cntr…/lbl1=val1,lbl2=val2…/ann1=val1,ann2=val2… where ns=namespace, dep=deployment, cntr=container, lbl=label, ann=annotation

The filter spec is interpreted as ‘must be in (ns1 OR ns2) AND (dep1 OR dep2) AND (cntr1 OR cntr2)…’ The log will be included only if the container matches at least one include filter and does not match any exclude filters. All parts of the filter are optional and can be omitted e.g. ns1//pod1 filters only for namespace ns1 and pod1. All names except label and annotation keys support ‘*‘ glob matching pattern.

e.g. —include ns1,ns2 (only namespaces ns1 and ns2) —include n*//p*/l=v* (pods with name beginning with ‘p’ in namespaces beginning with ‘n’ and having label ‘l’ with value beginning with ‘v’.)

istioctl bug-report [flags]

istioctl bug-report version

Prints out build version information

istioctl bug-report version [flags]

istioctl dashboard

Access to Istio web UIs

istioctl dashboard [flags]

istioctl dash [flags]
istioctl d [flags]

istioctl dashboard controlz

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

istioctl dashboard controlz [<type>/]<name>[.<namespace>] [flags]

Examples

  # Open ControlZ web UI for the istiod-123-456.istio-system pod
  istioctl dashboard controlz istiod-123-456.istio-system
  # Open ControlZ web UI for the istiod-56dd66799-jfdvs pod in a custom namespace
  istioctl dashboard controlz istiod-123-456 -n custom-ns
  # Open ControlZ web UI for any Istiod pod
  istioctl dashboard controlz deployment/istiod.istio-system
  # with short syntax
  istioctl dash controlz pilot-123-456.istio-system
  istioctl d controlz pilot-123-456.istio-system

istioctl dashboard envoy

Open the Envoy admin dashboard for a sidecar

istioctl dashboard envoy [<type>/]<name>[.<namespace>] [flags]

Examples

  # Open Envoy dashboard for the productpage-123-456.default pod
  istioctl dashboard envoy productpage-123-456.default
  # Open Envoy dashboard for one pod under a deployment
  istioctl dashboard envoy deployment/productpage-v1
  # with short syntax
  istioctl dash envoy productpage-123-456.default
  istioctl d envoy productpage-123-456.default

istioctl dashboard grafana

Open Istio’s Grafana dashboard

istioctl dashboard grafana [flags]

Examples

  istioctl dashboard grafana
  # with short syntax
  istioctl dash grafana
  istioctl d grafana

istioctl dashboard jaeger

Open Istio’s Jaeger dashboard

istioctl dashboard jaeger [flags]

Examples

  istioctl dashboard jaeger
  # with short syntax
  istioctl dash jaeger
  istioctl d jaeger

istioctl dashboard kiali

Open Istio’s Kiali dashboard

istioctl dashboard kiali [flags]

Examples

  istioctl dashboard kiali
  # with short syntax
  istioctl dash kiali
  istioctl d kiali

istioctl dashboard prometheus

Open Istio’s Prometheus dashboard

istioctl dashboard prometheus [flags]

Examples

  istioctl dashboard prometheus
  # with short syntax
  istioctl dash prometheus
  istioctl d prometheus

istioctl dashboard zipkin

Open Istio’s Zipkin dashboard

istioctl dashboard zipkin [flags]

Examples

  istioctl dashboard zipkin
  # with short syntax
  istioctl dash zipkin
  istioctl d zipkin

istioctl experimental

Experimental commands that may be modified or deprecated

istioctl experimental add-to-mesh

‘istioctl experimental add-to-mesh’ restarts pods with an Istio sidecar or configures meshed pod access to external services. Use ‘add-to-mesh’ as an alternate to namespace-wide auto injection for troubleshooting compatibility.

The ‘remove-from-mesh’ command can be used to restart with the sidecar removed.

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

istioctl experimental add-to-mesh [flags]

istioctl experimental add [flags]

Examples

  # Restart all productpage pods with an Istio sidecar
  istioctl experimental add-to-mesh service productpage
  # Restart just pods from the productpage-v1 deployment
  istioctl experimental add-to-mesh deployment productpage-v1
  # Restart just pods from the details-v1 deployment
  istioctl x add deployment details-v1
  # Control how meshed pods see an external service
  istioctl experimental add-to-mesh external-service vmhttp 172.12.23.125,172.12.23.126 \
   http:9080 tcp:8888 --labels app=test,version=v1 --annotations env=stage --serviceaccount stageAdmin

istioctl experimental add-to-mesh deployment

‘istioctl experimental add-to-mesh deployment’ restarts pods with the Istio sidecar. Use ‘add-to-mesh’ to test deployments for compatibility with Istio. It can be used instead of namespace-wide auto-injection of sidecars and is especially helpful for compatibility testing.

If your deployment does not function after using ‘add-to-mesh’ you must re-deploy it and troubleshoot it for Istio compatibility. See

See also ‘istioctl experimental remove-from-mesh deployment’ which does the reverse.

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

istioctl experimental add-to-mesh deployment <deployment> [flags]

istioctl experimental add-to-mesh deploy <deployment> [flags]
istioctl experimental add-to-mesh dep <deployment> [flags]

Examples

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

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.

See also ‘istioctl experimental remove-from-mesh external-service’ which does the reverse.

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

istioctl experimental add-to-mesh external-service <svcname> <ip> [name1:]port1 [[name2:]port2] ... [flags]

istioctl experimental add-to-mesh es <svcname> <ip> [name1:]port1 [[name2:]port2] ... [flags]

Examples

 # Control how meshed pods contact 172.12.23.125 and .126
  istioctl experimental add-to-mesh external-service vmhttp 172.12.23.125,172.12.23.126 \
   http:9080 tcp:8888 --labels app=test,version=v1 --annotations env=stage --serviceaccount stageAdmin

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. It can be used instead of namespace-wide auto-injection of sidecars and is especially helpful for compatibility testing.

If your service does not function after using ‘add-to-mesh’ you must re-deploy it and troubleshoot it for Istio compatibility. See https://istio.io/v1.10/docs/ops/deployment/requirements/

See also ‘istioctl experimental remove-from-mesh service’ which does the reverse.

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

istioctl experimental add-to-mesh service <service> [flags]

istioctl experimental add-to-mesh svc <service> [flags]

Examples

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

istioctl experimental authz

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

istioctl experimental authz check

Check prints the AuthorizationPolicy applied to a pod by directly checking the Envoy configuration of the pod. The command is especially useful for inspecting the policy propagation from Istiod to Envoy and the final AuthorizationPolicy list merged from multiple sources (mesh-level, namespace-level and workload-level).

The command also supports reading from a standalone config dump file with flag -f.

istioctl experimental authz check [<type>/]<name>[.<namespace>] [flags]

Examples

  # Check AuthorizationPolicy applied to pod httpbin-88ddbcfdd-nt5jb:
  istioctl x authz check httpbin-88ddbcfdd-nt5jb
  # Check AuthorizationPolicy applied to one pod under a deployment
  istioctl proxy-status deployment/productpage-v1
  # Check AuthorizationPolicy from Envoy config dump file:
  istioctl x authz check -f httpbin_config_dump.json

istioctl experimental config

Configure istioctl defaults

Examples

  # list configuration parameters
  istioctl config list

istioctl experimental config list

List istio configurable defaults

istioctl experimental config list [flags]

istioctl experimental create-remote-secret

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

istioctl experimental create-remote-secret [flags]

Examples

  # Create a secret to access cluster c0's apiserver and install it in cluster c1.
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 \
    | kubectl --kubeconfig=c1.yaml apply -f -
  # Delete a secret that was previously installed in c1
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 \
    | kubectl --kubeconfig=c1.yaml delete -f -
  # Create a secret access a remote cluster with an auth plugin
  istioctl --kubeconfig=c0.yaml x create-remote-secret --name c0 --auth-type=plugin --auth-plugin-name=gcp \
    | kubectl --kubeconfig=c1.yaml apply -f -

istioctl experimental describe

istioctl experimental describe [flags]

istioctl experimental des [flags]

istioctl experimental describe pod

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

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

istioctl experimental describe pod <pod> [flags]

Examples

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

istioctl experimental describe service <svc> [flags]

istioctl experimental describe svc <svc> [flags]

Examples

  istioctl experimental describe service productpage

istioctl experimental injector

List sidecar injector and sidecar versions

istioctl experimental injector [flags]

Examples

  istioctl experimental injector list

List sidecar injector and sidecar versions

  istioctl experimental injector list

istioctl experimental internal-debug

Retrieves the debug information from Istiod or Pods in the mesh using the service account from the pod if —cert-dir is empty. By default it will use the default serviceAccount from (istio-system) namespace if the pod is not specified.

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

istioctl experimental internal-debug [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve sync status for all Envoys in a mesh
  istioctl x internal-debug syncz
  # Retrieve sync diff for a single Envoy and Istiod
  istioctl x internal-debug syncz istio-egressgateway-59585c5b9c-ndc59.istio-system
  # SECURITY OPTIONS
  # Retrieve syncz debug information directly from the control plane, using token security
  # (This is the usual way to get the debug information with an out-of-cluster control plane.)
  istioctl x internal-debug syncz --xds-address istio.cloudprovider.example.com:15012
  # Retrieve syncz debug information via Kubernetes config, using token security
  # (This is the usual way to get the debug information with an in-cluster control plane.)
  istioctl x internal-debug syncz
  # Retrieve syncz debug information directly from the control plane, using RSA certificate security
  # (Certificates must be obtained before this step.  The --cert-dir flag lets istioctl bypass the Kubernetes API server.)
  istioctl x internal-debug syncz --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs
  # Retrieve syncz information via XDS from specific control plane in multi-control plane in-cluster configuration
  # (Select a specific control plane in an in-cluster canary Istio configuration.)
  istioctl x internal-debug syncz --xds-label istio.io/rev=default

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”.

istioctl experimental kube-uninject [flags]

Examples

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

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.

istioctl experimental metrics <workload name>...

istioctl experimental m <workload name>...

Examples

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

istioctl experimental precheck

precheck inspects a Kubernetes cluster for Istio install and upgrade requirements.

istioctl experimental precheck [flags]

Examples

  # Verify that Istio can be installed or upgraded
  istioctl x precheck
  # Check only a single namespace
  istioctl x precheck --namespace default

istioctl experimental proxy-status

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

istioctl experimental proxy-status [<type>/]<name>[.<namespace>] [flags]

istioctl experimental ps [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve sync status for all Envoys in a mesh
  istioctl x proxy-status
  # Retrieve sync diff for a single Envoy and Istiod
  istioctl x proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system
  # SECURITY OPTIONS
  # Retrieve proxy status information directly from the control plane, using token security
  # (This is the usual way to get the proxy-status with an out-of-cluster control plane.)
  istioctl x ps --xds-address istio.cloudprovider.example.com:15012
  # Retrieve proxy status information via Kubernetes config, using token security
  # (This is the usual way to get the proxy-status with an in-cluster control plane.)
  istioctl x proxy-status
  # Retrieve proxy status information directly from the control plane, using RSA certificate security
  # (Certificates must be obtained before this step.  The --cert-dir flag lets istioctl bypass the Kubernetes API server.)
  istioctl x ps --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs
  # Retrieve proxy status information via XDS from specific control plane in multi-control plane in-cluster configuration
  # (Select a specific control plane in an in-cluster canary Istio configuration.)
  istioctl x ps --xds-label istio.io/rev=default

istioctl experimental remove-from-mesh

‘istioctl experimental remove-from-mesh’ restarts pods without an Istio sidecar or removes external service access configuration. Use ‘remove-from-mesh’ to quickly test uninjected behavior as part of compatibility troubleshooting. The ‘add-to-mesh’ command can be used to add or restore the sidecar.

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

istioctl experimental remove-from-mesh [flags]

istioctl experimental rm [flags]

Examples

  # Restart all productpage pods without an Istio sidecar
  istioctl experimental remove-from-mesh service productpage
  # Restart all details-v1 pods without an Istio sidecar
  istioctl x rm service details-v1
  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm deploy ratings-v1

istioctl experimental remove-from-mesh deployment

‘istioctl experimental remove-from-mesh deployment’ restarts pods with the Istio sidecar un-injected. ‘remove-from-mesh’ is a compatibility troubleshooting tool.

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

istioctl experimental remove-from-mesh deployment <deployment> [flags]

istioctl experimental remove-from-mesh deploy <deployment> [flags]
istioctl experimental remove-from-mesh dep <deployment> [flags]

Examples

  # Restart all productpage-v1 pods without an Istio sidecar
  istioctl experimental remove-from-mesh deployment productpage-v1
  istioctl x remove-from-mesh deploy details-v1
  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm dep ratings-v1

istioctl experimental remove-from-mesh external-service

‘istioctl experimental remove-from-mesh external-service’ removes the ServiceEntry and the Kubernetes Service for the specified external service (e.g. services running on a VM) from Istio service mesh. The typical usage scenario is Mesh Expansion on VMs.

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

istioctl experimental remove-from-mesh external-service <svcname> [flags]

istioctl experimental remove-from-mesh es <svcname> [flags]

Examples

  # Remove "vmhttp" service entry rules
  istioctl experimental remove-from-mesh external-service vmhttp
  # Remove "vmhttp" service entry rules
  istioctl x remove-from-mesh es vmhttp
  # Remove "vmhttp" service entry rules
  istioctl x rm es vmhttp

istioctl experimental remove-from-mesh service

‘istioctl experimental remove-from-mesh service’ restarts pods with the Istio sidecar un-injected. ‘remove-from-mesh’ is a compatibility troubleshooting tool.

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

istioctl experimental remove-from-mesh service <service> [flags]

istioctl experimental remove-from-mesh svc <service> [flags]

Examples

  # Restart all productpage pods without an Istio sidecar
  istioctl experimental remove-from-mesh service productpage
  # Restart all details-v1 pods without an Istio sidecar
  istioctl x remove-from-mesh svc details-v1
  # Restart all ratings-v1 pods without an Istio sidecar
  istioctl x rm svc ratings-v1

istioctl experimental revision

The revision command provides a revision centric view of istio deployments. It provides insight into IstioOperator CRs defining the revision, istiod and gateway pods which are part of deployment of a particular revision.

istioctl experimental revision describe

Show information about a revision, including customizations, istiod version and which pods/gateways are using it.

istioctl experimental revision describe [flags]

Examples

  # View the details of a revision named 'canary'
  istioctl experimental revision describe canary
  # View the details of a revision named 'canary' and also the pods
  # under that particular revision
  istioctl experimental revision describe canary -v
  # Get details about a revision in json format (default format is human-friendly table format)
  istioctl experimental revision describe canary -v -o json

istioctl experimental revision list

Show list of control plane and gateway revisions that are currently installed in cluster

istioctl experimental revision list [flags]

Examples

  # View summary of revisions installed in the current cluster
  # which can be overridden with --context parameter.
  istioctl experimental revision list
  # View list of revisions including customizations, istiod and gateway pods
  istioctl experimental revision list -v

istioctl experimental revision tag

Command group used to interact with revision tags. Revision tags allow for the creation of mutable aliases referring to control plane revisions for sidecar injection.

With revision tags, rather than relabeling a namespace from “istio.io/rev=revision-a” to “istio.io/rev=revision-b” to change which control plane revision handles injection, it’s possible to create a revision tag “prod” and label our namespace “istio.io/rev=prod”. The “prod” revision tag could point to “1-7-6” initially and then be changed to point to “1-8-1” at some later point.

This allows operators to change which Istio control plane revision should handle injection for a namespace or set of namespaces without manual relabeling of the “istio.io/rev” tag.

istioctl experimental revision tag [flags]

istioctl experimental revision tag generate

Create a revision tag and output to the command’s stdout. Tag an Istio control plane revision for use with namespace istio.io/rev injection labels.

istioctl experimental revision tag generate <revision-tag> [flags]

Examples

 # Create a revision tag from the "1-8-0" revision
 istioctl x revision tag generate prod --revision 1-8-0 > tag.yaml
 # Apply the tag to cluster
 kubectl apply -f tag.yaml
 # Point namespace "test-ns" at the revision pointed to by the "prod" revision tag
 kubectl label ns test-ns istio.io/rev=prod
 # Rollout namespace "test-ns" to update workloads to the "1-8-0" revision
 kubectl rollout restart deployments -n test-ns

istioctl experimental revision tag list

List existing revision tags

istioctl experimental revision tag list [flags]

istioctl experimental revision tag show [flags]

Examples

istioctl x revision tag list

istioctl experimental revision tag remove

Remove Istio control plane revision tag.

Removing a revision tag should be done with care. Removing a revision tag will disrupt sidecar injection in namespaces that reference the tag in an “istio.io/rev” label. Verify that there are no remaining namespaces referencing a revision tag before removing using the “istioctl x revision tag list” command.

istioctl experimental revision tag remove <revision-tag> [flags]

istioctl experimental revision tag delete <revision-tag> [flags]

Examples

 # Remove the revision tag "prod"
    istioctl x revision tag remove prod

istioctl experimental revision tag set

Create or modify revision tags. Tag an Istio control plane revision for use with namespace istio.io/rev injection labels.

istioctl experimental revision tag set <revision-tag> [flags]

Examples

 # Create a revision tag from the "1-8-0" revision
 istioctl x revision tag set prod --revision 1-8-0
 # Point namespace "test-ns" at the revision pointed to by the "prod" revision tag
 kubectl label ns test-ns istio.io/rev=prod
 # Change the revision tag to reference the "1-8-1" revision
 istioctl x revision tag prod --revision 1-8-1 --overwrite
 # Rollout namespace "test-ns" to update workloads to the "1-8-1" revision
 kubectl rollout restart deployments -n test-ns

istioctl experimental uninstall

The uninstall command uninstalls Istio from a cluster

istioctl experimental uninstall [flags]

Examples

  # Uninstall a single control plane by revision
  istioctl x uninstall --revision foo
  # Uninstall a single control plane by iop file
  istioctl x uninstall -f iop.yaml
  # Uninstall all control planes and shared resources
  istioctl x uninstall --purge

istioctl experimental version

Prints out build version information

istioctl experimental version [flags]

Examples

# Retrieve version information directly from the control plane, using token security
# (This is the usual way to get the control plane version with an out-of-cluster control plane.)
istioctl x version --xds-address istio.cloudprovider.example.com:15012
# Retrieve version information via Kubernetes config, using token security
# (This is the usual way to get the control plane version with an in-cluster control plane.)
istioctl x version
# Retrieve version information directly from the control plane, using RSA certificate security
# (Certificates must be obtained before this step.  The --cert-dir flag lets istioctl bypass the Kubernetes API server.)
istioctl x version --xds-address istio.example.com:15012 --cert-dir ~/.istio-certs
# Retrieve version information via XDS from specific control plane in multi-control plane in-cluster configuration
istioctl x version --xds-label istio.io/rev=default

istioctl experimental wait

Waits for the specified condition to be true of an Istio resource.

istioctl experimental wait [flags] <type> <name>[.<namespace>]

Examples

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

istioctl experimental workload

Commands to assist in configuring and deploying workloads running on VMs and other non-Kubernetes environments

Examples

  # workload group yaml generation
  workload group create
  # workload entry configuration generation
  workload entry configure

istioctl experimental workload entry

entry configure -f workloadgroup.yaml -o outputDir

istioctl experimental workload entry configure

Generates all the required configuration files for workload instance on a VM or non-Kubernetes environment from a WorkloadGroup artifact. This includes a MeshConfig resource, the cluster.env file, and necessary certificates and security tokens. Configure requires either the WorkloadGroup artifact path or its location on the API server.

istioctl experimental workload entry configure [flags]

Examples

  # configure example using a local WorkloadGroup artifact
  configure -f workloadgroup.yaml -o config
  # configure example using the API server
  configure --name foo --namespace bar -o config

istioctl experimental workload group

Commands dealing with WorkloadGroup resources

Examples

group create --name foo --namespace bar --labels app=foobar

istioctl experimental workload group create

Creates a WorkloadGroup resource that provides a template for associated WorkloadEntries. The default output is serialized YAML, which can be piped into ‘kubectl apply -f -‘ to send the artifact to the API Server.

istioctl experimental workload group create [flags]

Examples

create --name foo --namespace bar --labels app=foo,bar=baz --ports grpc=3550,http=8080 --annotations annotation=foobar --serviceAccount sa

istioctl install

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

istioctl apply [flags]

Examples

  # Apply a default Istio installation
  istioctl install
  # Enable Tracing
  istioctl install --set meshConfig.enableTracing=true
  # Generate the demo profile and don't wait for confirmation
  istioctl install --set profile=demo --skip-confirmation
  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl install --set "values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/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.

istioctl kube-inject [flags]

Examples

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

The manifest command generates and diffs Istio manifests.

istioctl manifest diff

The diff subcommand compares manifests from two files or directories. The output is a list of changed paths with the value changes shown as OLD-VALUE -> NEW-VALUE. List order changes are shown as [OLD-INDEX->NEW-INDEX], with ? used where a list item is added or removed.

istioctl manifest diff <file|dir> <file|dir> [flags]

istioctl manifest generate

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

istioctl manifest generate [flags]

Examples

  # Generate a default Istio installation
  istioctl manifest generate
  # Enable Tracing
  istioctl manifest generate --set meshConfig.enableTracing=true
  # Generate the demo profile
  istioctl manifest generate --set profile=demo
  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl manifest generate --set "values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default"

istioctl manifest install

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

istioctl manifest install [flags]

istioctl manifest apply [flags]

Examples

  # Apply a default Istio installation
  istioctl install
  # Enable Tracing
  istioctl install --set meshConfig.enableTracing=true
  # Generate the demo profile and don't wait for confirmation
  istioctl install --set profile=demo --skip-confirmation
  # To override a setting that includes dots, escape them with a backslash (\).  Your shell may require enclosing quotes.
  istioctl install --set "values.sidecarInjectorWebhook.injectedAnnotations.container\.apparmor\.security\.beta\.kubernetes\.io/istio-proxy=runtime/default"

istioctl operator

The operator command installs, dumps, removes and shows the status of the operator controller.

istioctl operator dump

The dump subcommand dumps the Istio operator controller manifest.

istioctl operator dump [flags]

istioctl operator init

The init subcommand installs the Istio operator controller in the cluster.

istioctl operator init [flags]

istioctl operator remove

The remove subcommand removes the Istio operator controller from the cluster.

istioctl operator remove [flags]

istioctl options

Displays istioctl global options

istioctl profile

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

Examples

istioctl profile list
istioctl install --set profile=demo  # Use a profile from the list

istioctl profile diff

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

istioctl profile diff <profile|file1.yaml> <profile|file2.yaml> [flags]

Examples

  # Profile diff by providing yaml files
  istioctl profile diff manifests/profiles/default.yaml manifests/profiles/demo.yaml
  # Profile diff by providing a profile name
  istioctl profile diff default demo

istioctl profile dump

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

istioctl profile dump [<profile>] [flags]

istioctl profile list

The list subcommand lists the available Istio configuration profiles.

istioctl profile list [flags]

istioctl proxy-config

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

Examples

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

istioctl proxy-config all

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

istioctl proxy-config all [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config a [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve summary about all configuration for a given pod from Envoy.
  istioctl proxy-config all <pod-name[.namespace]>
  # Retrieve full cluster dump as JSON
  istioctl proxy-config all <pod-name[.namespace]> -o json
  # Retrieve full cluster dump with short syntax
  istioctl pc a <pod-name[.namespace]>
  # Retrieve cluster summary without using Kubernetes API
  ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
  istioctl proxy-config all --file envoy-config.json

istioctl proxy-config bootstrap

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

istioctl proxy-config bootstrap [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config b [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve full bootstrap configuration for a given pod from Envoy.
  istioctl proxy-config bootstrap <pod-name[.namespace]>
  # Retrieve full bootstrap without using Kubernetes API
  ssh <user@hostname> 'curl localhost:15000/config_dump' > envoy-config.json
  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.

istioctl proxy-config cluster [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config clusters [<type>/]<name>[.<namespace>] [flags]
istioctl proxy-config c [<type>/]<name>[.<namespace>] [flags]

Examples

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

istioctl proxy-config endpoint [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config endpoints [<type>/]<name>[.<namespace>] [flags]
istioctl proxy-config ep [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve full endpoint configuration for a given pod from Envoy.
  istioctl proxy-config endpoint <pod-name[.namespace]>
  # Retrieve endpoint summary for endpoint with port 9080.
  istioctl proxy-config endpoint <pod-name[.namespace]> --port 9080
  # Retrieve full endpoint with a address (172.17.0.2).
  istioctl proxy-config endpoint <pod-name[.namespace]> --address 172.17.0.2 -o json
  # Retrieve full endpoint with a cluster name (outbound|9411||zipkin.istio-system.svc.cluster.local).
  istioctl proxy-config endpoint <pod-name[.namespace]> --cluster "outbound|9411||zipkin.istio-system.svc.cluster.local" -o json
  # Retrieve full endpoint with the status (healthy).
  istioctl proxy-config endpoint <pod-name[.namespace]> --status healthy -ojson
  # Retrieve endpoint summary without using Kubernetes API
  ssh <user@hostname> 'curl localhost:15000/clusters?format=json' > envoy-clusters.json
  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.

istioctl proxy-config listener [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config listeners [<type>/]<name>[.<namespace>] [flags]
istioctl proxy-config l [<type>/]<name>[.<namespace>] [flags]

Examples

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

istioctl proxy-config log [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config o [<type>/]<name>[.<namespace>] [flags]

Examples

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

istioctl proxy-config route

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

istioctl proxy-config route [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config routes [<type>/]<name>[.<namespace>] [flags]
istioctl proxy-config r [<type>/]<name>[.<namespace>] [flags]

Examples

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

istioctl proxy-config secret

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

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

istioctl proxy-config secret [<type>/]<name>[.<namespace>] [flags]

istioctl proxy-config secrets [<type>/]<name>[.<namespace>] [flags]
istioctl proxy-config s [<type>/]<name>[.<namespace>] [flags]

Examples

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

istioctl proxy-status

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

istioctl proxy-status [<type>/]<name>[.<namespace>] [flags]

istioctl ps [<type>/]<name>[.<namespace>] [flags]

Examples

  # Retrieve sync status for all Envoys in a mesh
  istioctl proxy-status
  # Retrieve sync diff for a single Envoy and Istiod
  istioctl proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system
  # Retrieve sync diff between Istiod and one pod under a deployment
  istioctl proxy-status deployment/productpage-v1
  # Write proxy config-dump to file, and compare to Istio control plane
  kubectl port-forward -n istio-system istio-egressgateway-59585c5b9c-ndc59 15000 &
  curl localhost:15000/config_dump > cd.json
  istioctl proxy-status istio-egressgateway-59585c5b9c-ndc59.istio-system --file cd.json

istioctl 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.

istioctl upgrade [flags]

istioctl validate

Validate Istio policy and rules files

istioctl validate -f FILENAME [options] [flags]

istioctl v -f FILENAME [options] [flags]

  # Validate bookinfo-gateway.yaml
  istioctl validate -f samples/bookinfo/networking/bookinfo-gateway.yaml
  # Validate bookinfo-gateway.yaml with shorthand syntax
  istioctl v -f samples/bookinfo/networking/bookinfo-gateway.yaml
  # Validate current deployments under 'default' namespace within the cluster
  kubectl get deployments -o yaml | istioctl validate -f -
  # Validate current services under 'default' namespace within the cluster
  kubectl get services -o yaml | istioctl validate -f -
  # Also see the related command 'istioctl analyze'
  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 an installation it will check for an IstioOperator resource and will verify if pods and services defined in it are present.

Note: For verifying whether your cluster is ready for Istio installation, see istioctl experimental precheck.

istioctl verify-install [-f <deployment or istio operator file>] [--revision <revision>] [flags]

Examples

  # Verify that Istio is installed correctly via Istio Operator
  istioctl verify-install
  # Verify the deployment matches a custom Istio deployment configuration
  istioctl verify-install -f $HOME/istio.yaml
  # Verify the deployment matches the Istio Operator deployment definition
  istioctl verify-install --revision <canary>
  # Verify the installation of specific revision
  istioctl verify-install -r 1-9-0

istioctl version

Prints out build version information

Environment variables