ISTIOCTL-EXPERIMENTAL-INTERNAL-DEBUG(1)

πŸ“¦ version 1.31.3, in nixos 26.05, nixpkgs unstable

πŸ¦‹ istioctl experimental internal-debug β€” the ISTIOCTL-EXPERIMENTAL-INTERNAL-DEBUG(1) manual page, bestie πŸ¦‹

okay so welcome to ISTIOCTL-EXPERIMENTAL-INTERNAL-DEBUG(1). This is the command that pulls the debug tea from Istio, and honestly it’s giving developer-tools main character energy. πŸ’–

πŸ’– NAME πŸ’–

istioctl-experimental-internal-debug β€” Retrieves the debug information of istio 🫢

✨ SYNOPSIS ✨

istioctl experimental internal-debug [/][.] [flags]

🌸 DESCRIPTION 🌸

Okay so what it does: 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. Periodt. πŸ’…

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

No cap, do not ship this to prod like it’s a finished look. It’s still in the group chat with β€œtyping…” energy. 😭

πŸ’… OPTIONS πŸ’…

  • --all[=false] β€” Send the same request to all instances of Istiod. Only applicable for in-cluster deployment. πŸ’«
  • --authority="" β€” XDS Subject Alternative Name (for example istiod.istio-system.svc). πŸͺͺ
  • --cert-dir="" β€” XDS Endpoint certificate directory. πŸŽ€
  • -h, --help[=false] β€” help for internal-debug. The little rescue button. 🫢
  • --insecure[=false] β€” Skip server certificate and domain verification. (NOT SECURE!) πŸ”₯
  • -L, --list[=false] β€” List all supported debug types. Your menu of debug snacks. πŸ“
  • --plaintext[=false] β€” Use plain-text HTTP/2 when connecting to server (no TLS). 🫧
  • -r, --revision="" β€” Control plane revision. 🧚
  • --timeout=30s β€” The duration to wait before failing. ⏳
  • --xds-address="" β€” XDS Endpoint. πŸ“
  • --xds-label="" β€” Istiod pod label selector. 🏷️
  • --xds-port=15012 β€” Istiod pod port. πŸ”Œ

πŸŽ€ OPTIONS INHERITED FROM PARENT COMMANDS πŸŽ€

  • --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 πŸ”₯

okay bestie, examples are the actual moment. Copy these exactly, no improv:

         # 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

         # List all supported debug types
         istioctl x internal-debug --list

         # 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

🌈 SEE ALSO 🌈


Auto generated by spf13/cobra in Jan β€” slay, and goodbye from ISTIOCTL-EXPERIMENTAL-INTERNAL-DEBUG(1) πŸ’‹βœ¨

πŸ“¦ where this page comes from