Project
dflow clusters:register
Attach a private cluster to the current workspace. The kubeconfig is sent once and is not printed.
dflow clusters:register --name NAME --region REGION --kubeconfig PATHFlags
--name required. --region required. --kubeconfig required. --idempotency-key optional. Globals.
What you see
The terminal prints aligned labels status, cluster, and operation. --name and --region are required. The region is 2 to 32 lowercase letters, digits, or hyphens. The kubeconfig must name a server. Exit 0 when the operation status is succeeded.
When it fails
A missing workspace exits 1. Exit 1: missing flags, a bad region, or a kubeconfig that cannot be read. Exit 2: auth. Exit 5: the check failed. Exit 6: a precondition, including a credential that was not stored. Exit 10: unreachable.
How is this guide?
Last updated on