gcloud run domain-mappings create - create domain mappings for Cloud Run for Anthos
gcloud run domain-mappings create --service=SERVICE (--domain=DOMAIN : --namespace=NAMESPACE) [--force-override] [--platform=PLATFORM; default="managed"] [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
Create domain mappings for Cloud Run for Anthos.
For domain mapping support with fully managed Cloud Run, use gcloud beta run domain-mappings create.
To create a Cloud Run domain mapping, run:
$ gcloud run domain-mappings create --service=myapp \ --domain=www.example.com
- --service=SERVICE
Create domain mapping for the given service.
- DomainMapping resource - Domain name is the ID of DomainMapping resource. The
arguments in this group can be used to specify the attributes of this resource.
This must be specified.
- --domain=DOMAIN
ID of the DomainMapping or fully qualified identifier for the DomainMapping. To set the domain attribute:
provide the argument --domain on the command line.
This flag argument must be specified if any of the other arguments in this group are specified.
- --namespace=NAMESPACE
Specific to Cloud Run for Anthos: Kubernetes namespace for the DomainMapping. To set the namespace attribute:
provide the argument --domain on the command line with a fully specified name;
provide the argument --namespace on the command line;
set the property run/namespace;
For Cloud Run on Kubernetes Engine, defaults to "default". Otherwise, defaults to project ID.;
provide the argument project on the command line;
set the property core/project.
- --force-override
Map this domain even if it is already mapped to another service.
- --platform=PLATFORM; default="managed"
Target platform for running commands. Alternatively, set the property [run/platform]. PLATFORM must be one of:
- managed
Fully managed version of Cloud Run. Not supported by this command.
- gke
Cloud Run for Anthos on Google Cloud. Use with the --cluster and --cluster-location flags or set the [run/cluster] and [run/cluster_location] properties to specify a cluster in a given zone.
- kubernetes
Use a Knative-compatible kubernetes cluster. Use with the --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting.
- Arguments to locate resources, depending on the platform used.
At most one of these can be specified:
- Only applicable if connecting to Cloud Run for Anthos deployed on Google Cloud.
Specify --platform=gke to use:
- Cluster resource - Kubernetes Engine cluster to connect to. 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;
- —
set the property run/cluster with a fully specified name;
- —
specify the cluster from a list of available clusters with a fully specified name;
- —
provide the argument --project on the command line;
- —
set the property core/project.
- --cluster=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;
set the property run/cluster;
specify the cluster from a list of available clusters.
- --cluster-location=CLUSTER_LOCATION
Zone in which the cluster is located. Alternatively, set the property [run/cluster_location]. To set the location attribute:
provide the argument --cluster on the command line with a fully specified name;
set the property run/cluster with a fully specified name;
specify the cluster from a list of available clusters with a fully specified name;
provide the argument --cluster-location on the command line;
set the property run/cluster_location;
specify the cluster location from a list of available zones.
- Only applicable if connecting to Cloud Run for Anthos deployed on VMware.
Specify --platform=kubernetes to use:
- --context=CONTEXT
The name of the context in your kubectl config file to use for connecting.
- --kubeconfig=KUBECONFIG
The absolute path to your kubectl config file. If not specified, the colon- or semicolon-delimited list of paths specified by $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to ~/.kube/config.
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.
These variants are also available:
$ gcloud alpha run domain-mappings create
$ gcloud beta run domain-mappings create