.TH "GCLOUD_ALPHA_CONTAINER_FLEET_INGRESS_DISABLE" 1



.SH "NAME"
.HP
gcloud alpha container fleet ingress disable \- disable Multi\-cluster Ingress Feature



.SH "SYNOPSIS"
.HP
\f5gcloud alpha container fleet ingress disable\fR [\fB\-\-force\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR This command disables Multi\-cluster Ingress Feature in a fleet.



.SH "EXAMPLES"

To disable the Ingress Feature, run:

.RS 2m
$ gcloud alpha container fleet ingress disable
.RE



.SH "FLAGS"

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

Force disablement. Bypasses any prompts for confirmation. When disabling the
entire feature, proceeds even if the feature is in use. Might result in
unexpected behavior.


.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 ingress disable
.RE

.RS 2m
$ gcloud beta container fleet ingress disable
.RE