ISTIOCTL-ZTUNNEL-CONFIG-SERVICE(1)

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

πŸ’… istioctl-ztunnel-config-service ✨

okay bestie, welcome to the istioctl-ztunnel-config-service page from the ISTIOCTL-ZTUNNEL-CONFIG-SERVICE(1) manual β€” yes the header says it twice, it's giving "mom said it's my turn on the xbox" energy, but we move. this is the glow-up guide where i explain the whole thing to you like we're texting at 2am 🫢


🌸 NAME 🌸

istioctl-ztunnel-config-service β€” literally just goes and retrieves the services for the Ztunnel pod you point at. that's the whole vibe check. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

istioctl ztunnel-config service [flags]

✨ DESCRIPTION ✨

so what this does is retrieve information about services for the Ztunnel instance. that's it, that's the task. iconic, no notes. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -f, --file="" β€” a Ztunnel config dump JSON file. hand it a file and it'll read from that instead, iykyk πŸ“
  • -h, --help[=false] β€” help for service. the classic "wait what does this do again" button πŸ™ˆ
  • --node="" β€” filter workloads by the node field. only wants the ones living on that node, picky queen πŸ’…
  • -o, --output="short" β€” output format, default is "short", and it has to be one of json|yaml|short. pick your aesthetic fr fr 🌈
  • --proxy-admin-port=15000 β€” the Ztunnel proxy admin port, defaults to 15000 πŸ”Œ
  • --service-namespace="" β€” filter services by the namespace field. keeps things scoped, very main character energy of it ✨

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

these are the hand-me-downs from the parent command and honestly they ate:

  • --as="" β€” username to impersonate for the operation. user could be a regular user or a service account in a namespace. dress up as someone else for a sec 🎭
  • --as-group=[] β€” group to impersonate for the operation, this flag can be repeated to specify multiple groups. repeat it, stack it, collect them all 🧚
  • --as-uid="" β€” UID to impersonate for the operation.
  • --context="" β€” Kubernetes configuration context. which world are we living in today 🌍
  • -i, --istioNamespace="istio-system" β€” Istio system namespace, defaults to "istio-system" πŸ’œ
  • --kubeclient-timeout="15s" β€” Kubernetes client timeout as a time.Duration string, defaults to 15 seconds. patience is a virtue but also there's a limit ⏳
  • -c, --kubeconfig="" β€” Kubernetes configuration file.
  • -n, --namespace="" β€” Kubernetes namespace.
  • --vklog=0 β€” number for the log level verbosity. like the -v flag. ex: --vklog=9. crank it up if you're nosy πŸ”

πŸ”₯ EXAMPLE πŸ”₯

okay watch closely bestie, here's how you actually use it:

  # Retrieve summary about services configuration for a randomly chosen ztunnel.
  istioctl ztunnel-config services

  # Retrieve full services dump of workloads for a given Ztunnel instance.
  istioctl ztunnel-config services <ztunnel-name[.namespace]> -o json
ngl the examples say services (plural) while the synopsis says service β€” that's what the page says, so that's what i'm telling you. copy it exactly, don't come for me 😭

🌺 SEE ALSO 🌺


and that's the page!! Auto generated by spf13/cobra (it wrote itself, king behavior), dated Jan 1980 which is literally so vintage of it πŸŽ€, brought to you as ISTIOCTL-ZTUNNEL-CONFIG-SERVICE(1). now go read your services, bestie, you're gonna slay πŸ¦‹βœ¨πŸ’…

πŸ“¦ where this page comes from