This page describes the required and optional parameters for
creating a Cloud Composer environment
gcloud beta composer environments create command.
When you create a new Cloud Composer environment, the following parameters are required. If you don't specify the parameters, environment creation fails.
|name||The name of the environment. The name must start with a lowercase letter followed by up to 62 lowercase letters, numbers, or hyphens, and cannot end with a hyphen.|
|location||The Compute Engine region where the environment is created. The beta release supports
When you create a new Cloud Composer environment, the following parameters are optional. If you do not specify the parameter, the default value is used.
|airflow-configs||A list of
|disk-size||The disk size in GB used for the node VMs. The minimum size is 20 GB.||100 GB|
|env-variables||A list of
|labels||User-specified labels that are attached to the environment and its resources.||none|
|machine-type||The Compute Engine machine type used for cluster instances. The machine type determines the number of CPUs and the amount of memory for your environment. Cloud Composer supports Compute Engine standard machine types.||n1-standard-1|
|network||The Virtual Private Cloud network ID that is used for machine communications. The network ID is required to specify a subnetwork. Shared Virtual Private Cloud is not currently supported.||default|
|node-count||The number of Kubernetes Engine nodes used to run the environment.||3|
|oauth-scopes||The set of Google API scopes made available on all of the node VMs.||https://www.googleapis.com/auth/cloud-platform|
|subnetwork||The Compute Engine subnetwork to which the environment is connected.||none|
|service-account||The Google Cloud Platform service account to be used by the node VMs. You cannot change the service account after the environment is created.||default|
|tags||The list of instance tags applied to all the node VMs. Tags are used to identify valid sources or targets for network firewalls. Each tag within the list must comply with RFC 1035.||none|