ISTIOCTL-PROXY-CONFIG-LISTENER(1)
β¨ 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 theaddressfield π―-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 ofjson|yaml|short(default isshort, 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 istrue!)
π« 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 (defaultistio-system, iconic) π--kubeclient-timeout="15s"β Kubernetes client timeout as atime.Durationstring, defaults to 15 seconds β±οΈ-c,--kubeconfig=""β Kubernetes configuration file π-n,--namespace=""β Kubernetes namespace π--proxy-admin-port=15000β Envoy proxy admin port (default15000) π--vklog=0β number for the log level verbosity. Like-vflag. 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 β
istioctl-proxy-config(1)β the parent, the main character π
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
- nixos 26.05: istioctl 1.29.2
- nixpkgs unstable: istioctl 1.31.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms