ISTIOCTL-ANALYZE(1)

💖 ISTIOCTL-ANALYZE(1) — istioctl-analyze

Bestie, this is the ISTIOCTL-ANALYZE(1) page from the istioctl manual. It's giving config-validation main character energy, and we're about to spill all the flag tea. 💅

🌸 NAME

istioctl-analyze — Analyze Istio configuration and print validation messages. No cap, that's the whole name.

✨ SYNOPSIS

istioctl analyze ... [flags]

🦋 DESCRIPTION

Okay so istioctl analyze literally analyzes Istio configuration and prints validation messages. Obsessed. For more information about message codes, refer to: https://istio.io/v1.31/docs/reference/config/analysis.

💅 OPTIONS

Here's the full menu, bestie — every flag, every default, no skips. 🍓

• -A, --all-namespaces[=false] — Analyze all namespaces. Every namespace gets the vibe check.
• --analyzer=[] — Select specific analyzers to run. Can be repeated. If not specified, all analyzers are run. Example vibe: istioctl analyze --analyzer "gateway.ConflictingGatewayAnalyzer".
• --color[=true] — Default true. Disable with =false or set $TERM to dumb. 🌈
• --failure-threshold=Error — The severity level of analysis at which to set a non-zero exit code. Valid values: [Info Warning Error].
• -h, --help[=false] — help for analyze. Your little rescue button.
• --ignore-unknown[=false] — Don't complain about un-parseable input documents, for cases where analyze should run only on k8s compliant inputs.
• -L, --list-analyzers[=false] — List the analyzers available to run. Suppresses normal execution. Show me the lineup.
• --meshConfigFile="" — Overrides the mesh config values to use for analysis.
• -o, --output="log" — Output format: one of [log json yaml].
• --output-threshold=Info — The severity level of analysis at which to display messages. Valid values: [Info Warning Error].
• -R, --recursive[=false] — > Removed flag alert: [Removed: The recursive flag has been removed and is hardcoded to true]. Process directory arguments recursively.
• --remote-contexts=[] — Kubernetes configuration contexts for remote clusters to be used in multi-cluster analysis. Not to be confused with '--context'. If unspecified, contexts are read from the remote secrets in the cluster.
• -r, --revision="default" — analyze a specific revision deployed. Periodt.
• -S, --suppress=[] — Suppress reporting a message code on a specific resource. Values are supplied in the form = (e.g. '--suppress "IST0102=DestinationRule primary-dr.default"'). Can be repeated. You can include the wildcard character '*' to support a partial match (e.g. '--suppress "IST0102=DestinationRule *.default" ).).
• --timeout=30s — The duration to wait before failing. Clock is ticking, bestie.
• -k, --use-kube[=true] — Use live Kubernetes cluster for analysis. Set --use-kube=false to analyze files only.
• -v, --verbose[=false] — Enable verbose output.

🎀 OPTIONS INHERITED FROM PARENT COMMANDS

These come from the parent command, so they're lowkey part of the family too. 🫶

• --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
• --as-group=[] — Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
• --as-uid="" — UID to impersonate for the operation.
• --context="" — Kubernetes configuration context.
• -i, --istioNamespace="istio-system" — Istio system namespace.
• --kubeclient-timeout="15s" — Kubernetes client timeout as a time.Duration string, defaults to 15 seconds.
• -c, --kubeconfig="" — Kubernetes configuration file.
• -n, --namespace="" — Kubernetes namespace.
• --vklog=0 — number for the log level verbosity. Like -v flag. ex: --vklog=9.

🔥 EXAMPLE

         # Analyze the current live cluster
         istioctl analyze

         # Analyze the current live cluster for a specific revision
         istioctl analyze --revision 1-16

         # Analyze the current live cluster, simulating the effect of applying additional yaml files
         istioctl analyze a.yaml b.yaml my-app-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

         # Run specific analyzer
         istioctl analyze --analyzer "gateway.ConflictingGatewayAnalyzer"

👑 SEE ALSO

istioctl(1)

---

This iconic page was auto generated by spf13/cobra, dated Jan 1980, and it's the ISTIOCTL-ANALYZE(1) manual page. Bye bestie, go analyze those configs! 💖