ISTIOCTL-EXPERIMENTAL-WORKLOAD-ENTRY(1)

📦 version 1.31.3, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

okay so bestie, welcome to istioctl-experimental-workload-entry — that’s the ISTIOCTL-EXPERIMENTAL-WORKLOAD-ENTRY(1) manual page, and it is literally the command group that deals with WorkloadEntry resources. Slay. 💅

🌸 SYNOPSIS 🌸

istioctl experimental workload entry [flags]

🦋 DESCRIPTION 🦋

istioctl experimental workload entry is the home base for commands dealing with WorkloadEntry resources. That’s the whole vibe: WorkloadEntry stuff, gathered together, no cap. ✨

🎀 OPTIONS 🎀

  • -h, --help[=false] — help for entry. 🫶

💅 OPTIONS INHERITED FROM PARENT COMMANDS 💅

These are the flags inherited from the parent command, bestie — every single one is here, and yes, the details matter:

  • --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 🌈

istioctl x workload entry configure -f workloadgroup.yaml -o outputDir

👑 SEE ALSO 👑

mwah 💋 — auto generated by spf13/cobra, dated Jan, and filed under ISTIOCTL-EXPERIMENTAL-WORKLOAD-ENTRY(1) 🫶✨

📦 where this page comes from