ISTIOCTL-ZTUNNEL-CONFIG-WORKLOAD(1)
okay bestie, welcome to the iconic ISTIOCTL-ZTUNNEL-CONFIG-WORKLOAD(1) page β the one thatβs all about istioctl-ztunnel-config-workload, and itβs lowkey here to hand you the workload config tea for a specified Ztunnel pod. π
β¨
π NAME π
istioctl-ztunnel-config-workload β retrieves workload configuration for the specified Ztunnel pod. Thatβs the vibe: youβre asking for the workload config of a Ztunnel pod, and this command is the main character that fetches it. π«Ά
β¨ SYNOPSIS β¨
istioctl ztunnel-config workload [/][.] [flags]
Yes, the [/][.] bit is literally part of the synopsis, bestie β keep it exactly like that, no cap. π¦
π¦ DESCRIPTION π¦
Retrieve information about workload configuration for the Ztunnel instance. Itβs giving βshow me the workload config for this Ztunnel,β and honestly? Same. πΈ
π OPTIONS π
Okay, hereβs the full flag lineup β every single one, no skips, fr fr. Keep the values literal, bestie; not me double-checking them so you donβt have to π.
--address=""β filter workloads by the address field.-f,--file=""β the Ztunnel config dump JSON file.-h,--help[=false]β help forworkload; yep, the[=false]notation is right there in the flag.--node=""β filter workloads by the node field.-o,--output="short"β output format: one ofjson|yaml|short; default isshort.--proxy-admin-port=15000β the Ztunnel proxy admin port,15000.--workload-namespace=""β filter workloads by the namespace field.--workload-node=""β filter workloads by node.
bestie, those flag values are literal βjson|yaml|short,istio-system,15s,15000, all of it. No improvising. π
𧬠OPTIONS INHERITED FROM PARENT COMMANDS π§¬
These came from the parent command and they still count here β inherited, not less important, periodt. π
--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 atime.Durationstring, defaults to 15 seconds.-c,--kubeconfig=""β Kubernetes configuration file.-n,--namespace=""β Kubernetes namespace.--vklog=0β number for the log level verbosity. Like-vflag. ex:--vklog=9.
π EXAMPLE π
Copy-paste energy only, bestie β here are the examples exactly as the page gives them: π
# Retrieve summary about workload configuration for a randomly chosen ztunnel.
istioctl ztunnel-config workload
# Retrieve summary of workloads on node XXXX for a given Ztunnel instance.
istioctl ztunnel-config workload <ztunnel-name[.namespace]> --node ambient-worker
# Retrieve full workload dump of workloads with address XXXX for a given Ztunnel instance.
istioctl ztunnel-config workload <ztunnel-name[.namespace]> --address 0.0.0.0 -o json
# Retrieve Ztunnel config dump separately and inspect from file.
kubectl exec -it $ZTUNNEL -n istio-system -- curl localhost:15000/config_dump > ztunnel-config.json
istioctl ztunnel-config workloads --file ztunnel-config.json
# Retrieve workload summary for a specific namespace
istioctl ztunnel-config workloads <ztunnel-name[.namespace]> --workload-namespace foo
# Retrieve workload info for a specific workload pod (auto-resolves to its ztunnel).
istioctl ztunnel-config workload <workload-pod-name[.namespace]>
π SEE ALSO π
istioctl-ztunnel-config(1)β the parent page, go check it out, iykyk. β
xoxo, bestie β this page was auto generated by spf13/cobra, dated Jan 1980 πβ¨π«Ά
π¦ where this page comes from
- 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