GCE Machine Configuration

The GCP Region and Zone that the VM will be deployed to. For example, us-east1-b.

The image project that the desired image families belong to.

The image family that the desired machine operating system belongs to.

The operating system that will be installed onto the VM.

The type of the disk attached to the VM. The available types may differ between regions.

The size of the disk attached to the VM, in Gigabytes.

The type of VM that will be deployed. Machine types determine the number of resources (vCPU, RAM, etc.) allocated for each node.

The VPC network that the VM will be created in. This value cannot be changed once the machine pool has been provisioned.

The VPC subnetwork that the VM will be created in. This value cannot be changed once the machine pool has been provisioned.

A custom username set as the default user of the GCE VM.

The desired external IP address for the GCE VM.

A list of OAuth2 scopes which allow the VM to access other GCP APIs.

By default, a VPC firewall rule is automatically created to expose a fixed set of ports within the VPC to facilitate communication between cluster nodes. This behavior can be disabled on a per machine pool basis, when clicking the Show Advanced option and disabling the Allow Internal Communication checkbox.

A list of ports to be opened externally to the wider internet. Open ports are defined at the machine pool level. Enabling this option will result in the automatic creation of a VPC firewall rule. This rule will be automatically deleted when the cluster or machine pool is deleted.

Tags is a list of network tags, which can be used to associate preexisting Firewall Rules with all VMs within a machine pool.

A comma-separated list of custom labels to be attached to all VMs within a given machine pool. Unlike Tags, Labels do not influence networking behavior and only serve to organize cloud resources.

A prefix that will be used when creating the firewall rule to expose ports publicly. Ideally, this should be a concatenation the machine pool name and the cluster name. This field must be set if the machine pool is configured to expose ports publicly, otherwise it can be omitted.

A prefix that will be used when creating the internal firewall rule which allows for communication between nodes within the cluster. If this field is omitted, no internal firewall rule will be created.