ISTIOCTL-WAYPOINT-APPLY(1)
π istioctl-waypoint-apply
okay so bestie, welcome to the istioctl-waypoint-apply page β that's the istioctl-waypoint-apply(1) manual entry, part of the whole istioctl waypoint universe. it's the one you want when you're like "i need a waypoint and i need it now" π¦
β¨ SYNOPSIS β¨
istioctl waypoint apply [flags]
that's it. that's the whole vibe. flags go after, obviously π
π DESCRIPTION π
Apply a waypoint configuration to the cluster. literally just that. you bring the config, it goes to the cluster, everyone slays. no cap π₯
πΈ OPTIONS πΈ
--enroll-namespace[=false]β if you set this, the namespace gets labeled with the waypoint name. it's giving "make it official" energy π«Ά--for=""β specify the traffic type. your options areall,none,service, andworkload. pick your fighter β-h,--help[=false]β help forapply. the classic "wait what does this do again" button π--overwrite[=false]β overwrite the existing Waypoint used by the namespace. ruthless. iconic. use with intention π-r,--revision=""β the revision to label the waypoint with π§-w,--wait[=false]β wait for the waypoint to be ready. patience is a virtue bestie π--waypoint-timeout=1m30sβ timeout for waiting for waypoint ready. so if you're waiting, this is how long you're waiting. one minute thirty seconds of pure anticipation β³
π OPTIONS INHERITED FROM PARENT COMMANDS π
these come from the parent command, so like, you didn't get them here but they're still yours to use π
--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. stack 'em π--as-uid=""β UID to impersonate for the operation πͺͺ--context=""β Kubernetes configuration context ποΈ-i,--istioNamespace="istio-system"β Istio system namespace. defaults toistio-system, the home base π--kubeclient-timeout="15s"β Kubernetes client timeout as atime.Durationstring, defaults to 15 seconds β±οΈ-c,--kubeconfig=""β Kubernetes configuration file π--name="waypoint"β name of the waypoint. defaults towaypoint(they really said "keep it simple") π-n,--namespace=""β Kubernetes namespace π--vklog=0β number for the log level verbosity. like-vflag. ex:--vklog=9. loud and proud π
π¦ EXAMPLE π¦
# Apply a waypoint to the current namespace
istioctl waypoint apply
# Apply a waypoint to a specific namespace and wait for it to be ready
istioctl waypoint apply --namespace default --wait
first one: current namespace, no thoughts, just vibes. second one: you picked default and you're waiting for it, main character energy fr fr π
π SEE ALSO π
istioctl-waypoint(1)β the parent, go say hi π«Ά
ngl bestie, read the flags before you go overwriting things β --overwrite is right there and it is not shy π
and that's the page!! auto generated by spf13/cobra, dated Jan 1980 (yes really, she's vintage β¨), and this is the ISTIOCTL-WAYPOINT-APPLY(1) manual β slay, you're done, go apply some waypoints π
π
π¦ 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