Google Compute Engine Node Template

google_compute_node_template (Terraform)

The Node Template in Compute Engine can be configured in Terraform with the resource name google_compute_node_template. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

sylvioneto/terraform_gcp

resource "google_compute_node_template" "soletenant_tmpl" {
  name      = "soletenant-template"
  region    = "us-central1"
  node_type = "n1-node-96-624"
}

niveklabs/google

resource "google_compute_node_template" "this" {
  description          = var.description
  name                 = var.name
  node_affinity_labels = var.node_affinity_labels
  node_type            = var.node_type
  project              = var.project

Parameters

• cpu_overcommit_type optional - string

CPU overcommit. Default value: "NONE" Possible values: ["ENABLED", "NONE"]

• creation_timestamp optional computed - string

Creation timestamp in RFC3339 text format.

• description optional - string

An optional textual description of the resource.

• id optional computed - string
• name optional - string

Name of the resource.

• node_affinity_labels optional - map from string to string

Labels to use for node affinity, which will be used in instance scheduling.

• node_type optional - string

Node type to use for nodes group that are created from this template. Only one of nodeTypeFlexibility and nodeType can be specified.

• project optional computed - string
• region optional computed - string

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

• self_link optional computed - string
• node_type_flexibility list block
  • cpus optional - string

  Number of virtual CPUs to use.

  • local_ssd optional computed - string

  Use local SSD

  • memory optional - string

  Physical memory available to the node, defined in MB.

• server_binding list block
  • type required - string

  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. Possible values: ["RESTART_NODE_ON_ANY_SERVER", "RESTART_NODE_ON_MINIMAL_SERVERS"]

• timeouts single block
  • create optional - string
  • delete optional - string

Explanation in Terraform Registry

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:

• API documentation
• How-to Guides
  • Sole-Tenant Nodes

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

google_compute_disk

Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.

google_compute_firewall

Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.

google_compute_instance

Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.

google_compute_project_metadata

Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.

google_compute_ssl_policy

Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.

google_compute_subnetwork

Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.