ISTIOCTL-EXPERIM...LOAD-GROUP-CREATE(1)

💅 ISTIOCTL-EXPERIMENTAL-WORKLOAD-GROUP-CREATE 💅

okay bestie, welcome to the istioctl-experimental-workload-group-create page — yes the title is a whole mouthful, the manpage machinery just truncated it up top, but we're saying the whole thing okurrr 💖

---

✨ NAME ✨

istioctl-experimental-workload-group-create — creates a WorkloadGroup resource that gives you a template for all the associated WorkloadEntries 🫶

---

🌸 SYNOPSIS 🌸

istioctl experimental workload group create [flags]

that's the whole vibe. flags go at the end, periodt.

---

🦋 DESCRIPTION 🦋

So what does this actually do? It creates a WorkloadGroup resource, and that resource is literally the template for its associated WorkloadEntries ✨ like a little blueprint that says "here's what my workloads look like" and then the WorkloadEntries follow along.

The default output is serialized YAML — and bestie that is the move, because you can just pipe it straight into kubectl apply -f - and send the artifact to the API Server. no cap, no extra steps. iconic behavior honestly 👑

---

🎀 OPTIONS 🎀

• -a, --annotations=[] — the annotations you want to slap onto the workload instances 💌
• -h, --help[=false] — help for create. your classic little helper 🥺
• -l, --labels=[] — the labels to apply to the workload instances; e.g. -l env=prod,vers=2 🏷️
• --locality="" — the locality associated with the endpoint 📍
• --name="" — the name of the workload group, yes you gotta give it a name bestie 💜
• -n, --namespace="" — the namespace that the workload instances will belong to 🗂️
• --network="" — Network enables Istio to group endpoints resident in the same L3 domain/network 🌐
• -p, --ports=[] — the incoming ports exposed by the workload instance 🔌
• -s, --serviceAccount="default" — the service identity to associate with the workload instances (defaults to default, as it should) 🪪
• -w, --weight=0 — the load balancing weight associated with the endpoint ⚖️

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these are the family hand-me-downs, still lowkey essential:

• --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 is istio-system) 🌌
• --kubeclient-timeout="15s" — Kubernetes client timeout as a time.Duration string, defaults to 15 seconds ⏳
• -c, --kubeconfig="" — Kubernetes configuration file 📄
• --vklog=0 — number for the log level verbosity. Like -v flag. ex: --vklog=9 🔊

---

🍓 EXAMPLE 🍓

okay here's the whole thing in action, copy-paste energy fr fr:

istioctl x workload group create --name foo --namespace bar --labels app=foo,bar=baz --ports grpc=3550,http=8080 --annotations annotation=foobar --serviceAccount sa

look at that. name, namespace, labels, ports, annotations, serviceAccount — all the little details doing their thing 💅✨

---

🧚 SEE ALSO 🧚

istioctl-experimental-workload-group(1) — go read the parent one too, bestie 🫶

---

heads up: this page is Auto generated by spf13/cobra, dated Jan — so yeah, the robots made it, we just gave it the glow-up 💖 stay slay, bye! 🌸🦋