.TH "GCLOUD_ALPHA_CONTAINER_HUB_CREATE" 1



.SH "NAME"
.HP
gcloud alpha container hub create \- create a fleet



.SH "SYNOPSIS"
.HP
\f5gcloud alpha container hub create\fR [\fB\-\-async\fR] [\fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR] [\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-binauthz\-evaluation\-mode\fR=\fIBINAUTHZ_EVALUATION_MODE\fR\ \fB\-\-binauthz\-policy\-bindings\fR=[\fIname\fR=\fIBINAUTHZ_POLICY\fR]\ \fB\-\-security\-posture\fR=\fISECURITY_POSTURE\fR\ \fB\-\-workload\-vulnerability\-scanning\fR=\fIWORKLOAD_VULNERABILITY_SCANNING\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR This command can fail for the following reasons:
.RS 2m
.IP "\(bu" 2m
The project specified does not exist.
.IP "\(bu" 2m
The project specified already has a fleet.
.IP "\(bu" 2m
The active account does not have permission to access the given project.
.RE
.sp



.SH "EXAMPLES"

To create a fleet in project \f5example\-foo\-bar\-1\fR with display name
\f5my\-fleet\fR, run:

.RS 2m
$ gcloud alpha container hub create \-\-display\-name=my\-fleet \e
    \-\-project=example\-foo\-bar\-1
.RE



.SH "FLAGS"

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

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

.TP 2m
\fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR

Display name of the fleet to be created (optional). 4\-30 characters,
alphanumeric and [ '"!\-] only.

.TP 2m
\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]

List of label KEY=VALUE pairs to add.

Keys must start with a lowercase character and contain only hyphens (\f5\-\fR),
underscores (\f5_\fR), lowercase characters, and numbers. Values must contain
only hyphens (\f5\-\fR), underscores (\f5_\fR), lowercase characters, and
numbers.

.TP 2m

Default cluster configurations to apply across the fleet.


.RS 2m
.TP 2m

Binary Authorization config.


.RS 2m
.TP 2m
\fB\-\-binauthz\-evaluation\-mode\fR=\fIBINAUTHZ_EVALUATION_MODE\fR

Configure binary authorization mode for clusters to onboard the fleet,

.RS 2m
$ gcloud alpha container hub create \e
    \-\-binauthz\-evaluation\-mode=policy\-bindings
.RE

\fIBINAUTHZ_EVALUATION_MODE\fR must be one of: \fBdisabled\fR,
\fBpolicy\-bindings\fR.

.TP 2m
\fB\-\-binauthz\-policy\-bindings\fR=[\fIname\fR=\fIBINAUTHZ_POLICY\fR]

The relative resource name of the Binary Authorization policy to audit and/or
enforce. GKE policies have the following format:
\f5projects/{project_number}/platforms/gke/policies/{policy_id}\fR.

.RE
.sp
.TP 2m

Security posture config.


.RS 2m
.TP 2m
\fB\-\-security\-posture\fR=\fISECURITY_POSTURE\fR

To apply standard security posture to clusters in the fleet,

.RS 2m
$ gcloud alpha container hub create \-\-security\-posture=standard
.RE

\fISECURITY_POSTURE\fR must be one of: \fBdisabled\fR, \fBstandard\fR,
\fBenterprise\fR.

.TP 2m
\fB\-\-workload\-vulnerability\-scanning\fR=\fIWORKLOAD_VULNERABILITY_SCANNING\fR

To apply standard vulnerability scanning to clusters in the fleet,

.RS 2m
$ gcloud alpha container hub create \e
    \-\-workload\-vulnerability\-scanning=standard
.RE

\fIWORKLOAD_VULNERABILITY_SCANNING\fR must be one of: \fBdisabled\fR,
\fBstandard\fR, \fBenterprise\fR.


.RE
.RE
.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 "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist. These variants are also available:

.RS 2m
$ gcloud container hub create
.RE

.RS 2m
$ gcloud beta container hub create
.RE