» google_compute_node_template

Represents a NodeTemplate resource. Node templates specify properties for creating sole-tenant nodes, such as node type, vCPU and memory requirements, node affinity labels, and region.

To get more information about NodeTemplate, see:

» Example Usage - Node Template Basic

data "google_compute_node_types" "central1a" {
  zone = "us-central1-a"
}

resource "google_compute_node_template" "template" {
  name      = "soletenant-tmpl"
  region    = "us-central1"
  node_type = data.google_compute_node_types.central1a.names[0]
}

» Example Usage - Node Template Server Binding

provider "google-beta" {
  region = "us-central1"
  zone   = "us-central1-a"
}

data "google_compute_node_types" "central1a" {
  provider = google-beta
  zone     = "us-central1-a"
}

resource "google_compute_node_template" "template" {
  provider = google-beta

  name      = "soletenant-with-licenses"
  region    = "us-central1"
  node_type = data.google_compute_node_types.central1a.names[0]

  node_affinity_labels = {
    foo = "baz"
  }

  server_binding {
    type = "RESTART_NODE_ON_MINIMAL_SERVERS"
  }
}

» Argument Reference

The following arguments are supported:


  • description - (Optional) An optional textual description of the resource.

  • name - (Optional) Name of the resource.

  • node_affinity_labels - (Optional) Labels to use for node affinity, which will be used in instance scheduling.

  • node_type - (Optional) Node type to use for nodes group that are created from this template. Only one of nodeTypeFlexibility and nodeType can be specified.

  • node_type_flexibility - (Optional) Flexible properties for the desired node type. Node groups that use this node template will create nodes of a type that matches these properties. Only one of nodeTypeFlexibility and nodeType can be specified. Structure is documented below.

  • server_binding - (Optional, Beta) The server binding policy for nodes using this template. Determines where the nodes should restart following a maintenance event. Structure is documented below.

  • region - (Optional) Region where nodes using the node template will be created. If it is not provided, the provider region is used.

  • project - (Optional) The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

The node_type_flexibility block supports:

  • cpus - (Optional) Number of virtual CPUs to use.

  • memory - (Optional) Physical memory available to the node, defined in MB.

  • local_ssd - Use local SSD

The server_binding block supports:

  • type - (Required) Type of server binding policy. If RESTART_NODE_ON_ANY_SERVER, nodes using this template will restart on any physical server following a maintenance event. If RESTART_NODE_ON_MINIMAL_SERVER, nodes using this template will restart on the same physical server following a maintenance event, instead of being live migrated to or restarted on a new physical server. This option may be useful if you are using software licenses tied to the underlying server characteristics such as physical sockets or cores, to avoid the need for additional licenses when maintenance occurs. However, VMs on such nodes will experience outages while maintenance is applied.

» Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

» Timeouts

This resource provides the following Timeouts configuration options:

  • create - Default is 4 minutes.
  • delete - Default is 4 minutes.

» Import

NodeTemplate can be imported using any of these accepted formats:

$ terraform import google_compute_node_template.default projects/{{project}}/regions/{{region}}/nodeTemplates/{{name}}
$ terraform import google_compute_node_template.default {{project}}/{{region}}/{{name}}
$ terraform import google_compute_node_template.default {{region}}/{{name}}
$ terraform import google_compute_node_template.default {{name}}

» User Project Overrides

This resource supports User Project Overrides.