ISTIOCTL-PROXY-CONFIG-LISTENER(1)

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

✨ istioctl-proxy-config-listener ✨

okay so bestie, this is the istioctl-proxy-config-listener(1) page β€” yes the whole name is a mouthful, we don't make the rules πŸ’… β€” and it's literally your backstage pass to peeking at the listener config of the Envoy sidecar chillin' in whatever pod you point at. let's get into it πŸŽ€


🌸 NAME 🌸

istioctl-proxy-config-listener β€” grabs the listener configuration for the Envoy in the pod you specify 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

istioctl proxy-config listener [/][.] [flags]

that's the shape of it, no notes ✨


πŸ’œ DESCRIPTION πŸ’œ

So basically: you want the tea β˜• on listener configuration for the Envoy instance running inside a specific pod? This command pulls all of that for you. It's giving "detective but make it DevOps" πŸ”πŸ’–


🌈 OPTIONS 🌈

  • --address="" β€” filters listeners by the address field 🎯
  • -f, --file="" β€” points to an Envoy config dump JSON file (yes, you can do this whole thing offline, obsessed) πŸ“
  • -h, --help[=false] β€” help for listener, the classic 🫢
  • -o, --output="short" β€” output format, one of json|yaml|short (default is short, precious and compact) πŸŽ€
  • --port=0 β€” filters listeners by the Port field πŸ”’
  • --type="" β€” filters listeners by the type field 🏷️
  • --verbose[=true] β€” output more information, for when you simply must know everything πŸ‘‘ (note the default here is true!)

πŸ’« OPTIONS INHERITED FROM PARENT COMMANDS πŸ’«

these come from the parent command, so they're always in the group chat:

  • --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 (default istio-system, iconic) 🏠
  • --kubeclient-timeout="15s" β€” Kubernetes client timeout as a time.Duration string, defaults to 15 seconds ⏱️
  • -c, --kubeconfig="" β€” Kubernetes configuration file πŸ“„
  • -n, --namespace="" β€” Kubernetes namespace 🌌
  • --proxy-admin-port=15000 β€” Envoy proxy admin port (default 15000) πŸ”Œ
  • --vklog=0 β€” number for the log level verbosity. Like -v flag. ex: --vklog=9 πŸ”Š

🌟 EXAMPLE 🌟

okay these are the actual moves, copy them exactly, no cap:

   # Retrieve summary about listener configuration for a given pod from Envoy.
   istioctl proxy-config listeners <pod-name[.namespace]>

   # Retrieve summary about listener configuration a pod under a deployment from Envoy.
   istioctl proxy-config deployment/<deployment-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

that last one is literally the "no cluster, no problem" hack and I'm obsessed πŸ˜­πŸ’–


⭐ SEE ALSO ⭐


bestie reminder: keep the flags exactly as written (-o json, --type HTTP, --address 0.0.0.0, etc.) β€” vibes are flexible, flag names are not πŸ™ˆ

and that's the whole page, slay πŸŽ€ this little beauty was auto generated by spf13/cobra and it's dated Jan 1980 β€” yes, ancient, a true vintage icon, we stan a timeless queen πŸ‘‘πŸ’€πŸ’–

πŸ“¦ where this page comes from