.TH "GCLOUD_ALPHA_CONTAINER_FLEET_MESH_ENABLE" 1



.SH "NAME"
.HP
gcloud alpha container fleet mesh enable \- enable Service Mesh Feature



.SH "SYNOPSIS"
.HP
\f5gcloud alpha container fleet mesh enable\fR [\fB\-\-fleet\-default\-member\-config\fR=\fIFLEET_DEFAULT_MEMBER_CONFIG\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Enable the Service Mesh Feature in a fleet.



.SH "EXAMPLES"

To enable the Service Mesh Feature, run:

.RS 2m
$ gcloud alpha container fleet mesh enable
.RE

To enable the Service Mesh Feature with a fleet\-level default Membership
configuration, run:

.RS 2m
$ gcloud alpha container fleet mesh enable \e
    \-\-fleet\-default\-member\-config=/path/to/service\-mesh.yaml
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-fleet\-default\-member\-config\fR=\fIFLEET_DEFAULT_MEMBER_CONFIG\fR

The path to a service\-mesh.yaml configuration file.

.RS 2m
To enable the Service Mesh Feature with a fleet\-level default
membership configuration, run:
.RE

.RS 2m
$ gcloud alpha container fleet mesh enable \e
\-\-fleet\-default\-member\-config=/path/to/service\-mesh.yaml
.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 fleet mesh enable
.RE

.RS 2m
$ gcloud beta container fleet mesh enable
.RE