.TH "GCLOUD_TELCO\-AUTOMATION_ORCHESTRATION\-CLUSTER_CREATE" 1



.SH "NAME"
.HP
gcloud telco\-automation orchestration\-cluster create \- create a telco automation orchestration cluster



.SH "SYNOPSIS"
.HP
\f5gcloud telco\-automation orchestration\-cluster create\fR (\fIORCHESTRATION_CLUSTER\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) [\fB\-\-async\fR] [\fB\-\-cidr\-blocks\fR=[\fIcidr\-block\fR=\fICIDR\-BLOCK\fR],[\fIdisplay\-name\fR=\fIDISPLAY\-NAME\fR]] [\fB\-\-cluster\-cidr\-block\fR=\fICLUSTER_CIDR_BLOCK\fR] [\fB\-\-cluster\-named\-range\fR=\fICLUSTER_NAMED_RANGE\fR] [\fB\-\-full\-management\-config\fR] [\fB\-\-master\-ipv4\-cidr\-block\fR=\fIMASTER_IPV4_CIDR_BLOCK\fR] [\fB\-\-services\-cidr\-block\fR=\fISERVICES_CIDR_BLOCK\fR] [\fB\-\-services\-named\-range\fR=\fISERVICES_NAMED_RANGE\fR] [\fB\-\-network\fR=\fINETWORK\fR\ :\ \fB\-\-subnet\fR=\fISUBNET\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Create a new telco automation orchestration cluster.



.SH "EXAMPLES"

To create an orchestration cluster called \f5test\-orchestrationCluster\fR in
location \f5us\-central1\fR, run:

.RS 2m
$ gcloud telco\-automation orchestration\-cluster create \e
    test\-orchestrationCluster \-\-location=us\-central1
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Orchestration Cluster resource \- Telco automation orchestration cluster to
create. 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 \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5orchestration_cluster\fR on the command line with a
fully specified name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIORCHESTRATION_CLUSTER\fR

ID of the Orchestration Cluster or fully qualified identifier for the
Orchestration Cluster.

To set the \f5orchestration_cluster\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5orchestration_cluster\fR on the command line.
.RE
.sp

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

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The location name.

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5orchestration_cluster\fR on the command line with a
fully specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.

.TP 2m
\fB\-\-cidr\-blocks\fR=[\fIcidr\-block\fR=\fICIDR\-BLOCK\fR],[\fIdisplay\-name\fR=\fIDISPLAY\-NAME\fR]

Master Authorized Network that supports multiple CIDR blocks. Allows access to
the k8s master from multiple blocks.

.TP 2m
\fB\-\-cluster\-cidr\-block\fR=\fICLUSTER_CIDR_BLOCK\fR

IP address range for the cluster pod IPs. Set to blank to have a range chosen
with the default size. Set to /netmask (e.g. /14) to have a range chosen with a
specific netmask. Set to a CIDR notation (e.g. 10.96.0.0/14) from the RFC\-1918
private networks (e.g. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to pick a
specific range to use.

.TP 2m
\fB\-\-cluster\-named\-range\fR=\fICLUSTER_NAMED_RANGE\fR

Name of the existing secondary range in the cluster's subnetwork to use for pod
IP addresses. Alternatively, cluster_cidr_block can be used to automatically
create a GKE\-managed one.

.TP 2m
\fB\-\-full\-management\-config\fR

This parameter is to marked true only if the management configuration arguments
which are provided, belong to full (Autopilot) cluster management.

.TP 2m
\fB\-\-master\-ipv4\-cidr\-block\fR=\fIMASTER_IPV4_CIDR_BLOCK\fR

/28 network that the control plane will use.

.TP 2m
\fB\-\-services\-cidr\-block\fR=\fISERVICES_CIDR_BLOCK\fR

IP address range for the cluster service IPs. Set to blank to have a range
chosen with the default size. Set to /netmask (e.g. /14) to have a range chosen
with a specific netmask. Set to a CIDR notation (e.g. 10.96.0.0/14) from the
RFC\-1918 private networks (e.g. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to
pick a specific range to use.

.TP 2m
\fB\-\-services\-named\-range\fR=\fISERVICES_NAMED_RANGE\fR

Name of the existing secondary range in the cluster's subnetwork to use for
service ClusterIPs. Alternatively, services_cidr_block can be used to
automatically create a GKE\-managed one.

.TP 2m
\fB\-\-network\fR=\fINETWORK\fR

Name of the VPC Network to put the GKE cluster and nodes in. The VPC will be
created if it doesn't exist.

.TP 2m
\fB\-\-subnet\fR=\fISUBNET\fR

Specifies the subnet that the interface will be part of. Network key must be
specified and the subnet must be a subnetwork of the specified network.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBtelcoautomation/v1\fR API. The full documentation for
this API can be found at:
https://cloud.google.com/blog/topics/telecommunications/network\-automation\-csps\-linus\-nephio\-cloud\-native



.SH "NOTES"

This variant is also available:

.RS 2m
$ gcloud alpha telco\-automation orchestration\-cluster create
.RE