gcloud cluster-director clusters export

NAME
gcloud cluster-director clusters export - exports a Cluster Director resource
SYNOPSIS
gcloud cluster-director clusters export (CLUSTER : --location=LOCATION) [--destination=DESTINATION] [--endpoint-mode=ENDPOINT_MODE] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
Exports a Cluster Director resource configuration to a YAML file.
EXAMPLES
To export a cluster my-cluster in location us-central1 to a YAML file, run: 
gcloud cluster-director clusters export my-cluster --location=us-central1 --destination=cluster-config.yaml
POSITIONAL ARGUMENTS
Cluster resource - Identifier. Name of the cluster to export. Format: cluster | projects/{project}/locations/{location}/clusters/{cluster} The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument cluster on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

CLUSTER
ID of the cluster or fully qualified identifier for the cluster.

To set the cluster attribute:

  • provide the argument cluster on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--location=LOCATION
Location ID of the cluster resource.

To set the location attribute:

  • provide the argument cluster on the command line with a fully specified name;
  • provide the argument --location on the command line.
FLAGS
--destination=DESTINATION
Path to a YAML file where the configuration will be exported. The exported data will not contain any output-only fields. Alternatively, you may omit this flag to write to standard output. For a schema describing the export/import format, see $CLOUDSDKROOT/lib/googlecloudsdk/schemas/…
--endpoint-mode=ENDPOINT_MODE
Specifies endpoint mode for a given command. Regional endpoints provide enhanced data residency and reliability by ensuring your request is handled entirely within the specified Google Cloud region. This differs from global endpoints, which may process parts of the request outside the target region. Overrides the default regional/endpoint_mode property value for this command invocation. ENDPOINT_MODE must be one of:
global
(Default) Use global rather than regional endpoints.
regional
Only use regional endpoints. An error will be raised if a regional endpoint is not available for a given command.
regional-preferred
Use regional endpoints when available, otherwise use global endpoints. Recommended for most users.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.

Run $ gcloud help for details.

API REFERENCE
This command uses the hypercomputecluster/v1 API. The full documentation for this API can be found at: https://docs.cloud.google.com/cluster-director/docs
REGIONAL ENDPOINTS
This command supports regional endpoints. To use regional endpoints for this command, use the --endpoint-mode=regional-preferred flag. To use regional endpoints by default, run $ gcloud config set regional/endpoint_mode regional-preferred.
NOTES
These variants are also available: 
gcloud alpha cluster-director clusters export
 
gcloud beta cluster-director clusters export