653 lines
28 KiB
Markdown
653 lines
28 KiB
Markdown
# Google Compute Engine VM module
|
|
|
|
This module can operate in two distinct modes:
|
|
|
|
- instance creation, with optional unmanaged group
|
|
- instance template creation
|
|
|
|
In both modes, an optional service account can be created and assigned to either instances or template. If you need a managed instance group when using the module in template mode, refer to the [`compute-mig`](../compute-mig) module.
|
|
|
|
## Examples
|
|
|
|
- [Instance using defaults](#instance-using-defaults)
|
|
- [Service account management](#service-account-management)
|
|
- [Disk management](#disk-management)
|
|
- [Disk sources](#disk-sources)
|
|
- [Disk types and options](#disk-types-and-options)
|
|
- [Network interfaces](#network-interfaces)
|
|
- [Internal and external IPs](#internal-and-external-ips)
|
|
- [Using Alias IPs](#using-alias-ips)
|
|
- [Using gVNIC](#using-gvnic)
|
|
- [Metadata](#metadata)
|
|
- [IAM](#iam)
|
|
- [Spot VM](#spot-vm)
|
|
- [Confidential compute](#confidential-compute)
|
|
- [Disk encryption with Cloud KMS](#disk-encryption-with-cloud-kms)
|
|
- [Instance template](#instance-template)
|
|
- [Instance group](#instance-group)
|
|
- [Instance Schedule](#instance-schedule)
|
|
- [Snapshot Schedules](#snapshot-schedules)
|
|
|
|
### Instance using defaults
|
|
|
|
The simplest example leverages defaults for the boot disk image and size, and uses a service account created by the module. Multiple instances can be managed via the `instance_count` variable.
|
|
|
|
```hcl
|
|
module "simple-vm-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
service_account_create = true
|
|
}
|
|
# tftest modules=1 resources=2 inventory=simple.yaml
|
|
```
|
|
|
|
### Service account management
|
|
|
|
VM service accounts can be managed in three different ways:
|
|
|
|
- You can let the module create a service account for you by setting `service_account_create = true`
|
|
- You can use an existing service account by setting `service_account_create = false` (the default value) and passing the full email address of the service account to the `service_account` variable. This is useful, for example, if you want to reuse the service account from another previously created instance, or if you want to create the service account manually with the `iam-service-account` module. In this case, you probably also want to set `service_account_scopes` to `cloud-platform`.
|
|
- Lastly, you can use the default compute service account by setting `service_account_crate = false`. Please note that using the default compute service account is not recommended.
|
|
|
|
```hcl
|
|
module "vm-managed-sa-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test1"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
service_account_create = true
|
|
}
|
|
|
|
module "vm-managed-sa-example2" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test2"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
service_account = module.vm-managed-sa-example.service_account_email
|
|
service_account_scopes = ["cloud-platform"]
|
|
}
|
|
|
|
# not recommended
|
|
module "vm-default-sa-example2" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test3"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
service_account_create = false
|
|
}
|
|
|
|
# tftest modules=3 resources=4 inventory=sas.yaml
|
|
```
|
|
|
|
### Disk management
|
|
|
|
#### Disk sources
|
|
|
|
Attached disks can be created and optionally initialized from a pre-existing source, or attached to VMs when pre-existing. The `source` and `source_type` attributes of the `attached_disks` variable allows several modes of operation:
|
|
|
|
- `source_type = "image"` can be used with zonal disks in instances and templates, set `source` to the image name or self link
|
|
- `source_type = "snapshot"` can be used with instances only, set `source` to the snapshot name or self link
|
|
- `source_type = "attach"` can be used for both instances and templates to attach an existing disk, set source to the name (for zonal disks) or self link (for regional disks) of the existing disk to attach; no disk will be created
|
|
- `source_type = null` can be used where an empty disk is needed, `source` becomes irrelevant and can be left null
|
|
|
|
This is an example of attaching a pre-existing regional PD to a new instance:
|
|
|
|
```hcl
|
|
module "vm-disks-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "${var.region}-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
attached_disks = [{
|
|
name = "repd-1"
|
|
size = 10
|
|
source_type = "attach"
|
|
source = "regions/${var.region}/disks/repd-test-1"
|
|
options = {
|
|
replica_zone = "${var.region}-c"
|
|
}
|
|
}]
|
|
service_account_create = true
|
|
}
|
|
# tftest modules=1 resources=2
|
|
```
|
|
|
|
And the same example for an instance template (where not using the full self link of the disk triggers recreation of the template)
|
|
|
|
```hcl
|
|
module "vm-disks-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "${var.region}-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
attached_disks = [{
|
|
name = "repd"
|
|
size = 10
|
|
source_type = "attach"
|
|
source = "https://www.googleapis.com/compute/v1/projects/${var.project_id}/regions/${var.region}/disks/repd-test-1"
|
|
options = {
|
|
replica_zone = "${var.region}-c"
|
|
}
|
|
}]
|
|
service_account_create = true
|
|
create_template = true
|
|
}
|
|
# tftest modules=1 resources=2
|
|
```
|
|
|
|
#### Disk types and options
|
|
|
|
The `attached_disks` variable exposes an `option` attribute that can be used to fine tune the configuration of each disk. The following example shows a VM with multiple disks
|
|
|
|
```hcl
|
|
module "vm-disk-options-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
attached_disks = [
|
|
{
|
|
name = "data1"
|
|
size = "10"
|
|
source_type = "image"
|
|
source = "image-1"
|
|
options = {
|
|
auto_delete = false
|
|
replica_zone = "europe-west1-c"
|
|
}
|
|
},
|
|
{
|
|
name = "data2"
|
|
size = "20"
|
|
source_type = "snapshot"
|
|
source = "snapshot-2"
|
|
options = {
|
|
type = "pd-ssd"
|
|
mode = "READ_ONLY"
|
|
}
|
|
}
|
|
]
|
|
service_account_create = true
|
|
}
|
|
# tftest modules=1 resources=4 inventory=disk-options.yaml
|
|
```
|
|
|
|
### Network interfaces
|
|
|
|
#### Internal and external IPs
|
|
|
|
By default VNs are create with an automatically assigned IP addresses, but you can change it through the `addresses` and `nat` attributes of the `network_interfaces` variable:
|
|
|
|
```hcl
|
|
module "vm-internal-ip" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "vm-internal-ip"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
addresses = { internal = "10.0.0.2" }
|
|
}]
|
|
}
|
|
|
|
module "vm-external-ip" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "vm-external-ip"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
nat = true
|
|
addresses = { external = "8.8.8.8" }
|
|
}]
|
|
}
|
|
# tftest modules=2 resources=2 inventory=ips.yaml
|
|
```
|
|
|
|
#### Using Alias IPs
|
|
|
|
This example shows how to add additional [Alias IPs](https://cloud.google.com/vpc/docs/alias-ip) to your VM.
|
|
|
|
```hcl
|
|
module "vm-with-alias-ips" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
alias_ips = {
|
|
alias1 = "10.16.0.10/32"
|
|
}
|
|
}]
|
|
}
|
|
# tftest modules=1 resources=1 inventory=alias-ips.yaml
|
|
```
|
|
|
|
#### Using gVNIC
|
|
|
|
This example shows how to enable [gVNIC](https://cloud.google.com/compute/docs/networking/using-gvnic) on your VM by customizing a `cos` image. Given that gVNIC needs to be enabled as an instance configuration and as a guest os configuration, you'll need to supply a bootable disk with `guest_os_features=GVNIC`. `SEV_CAPABLE`, `UEFI_COMPATIBLE` and `VIRTIO_SCSI_MULTIQUEUE` are enabled implicitly in the `cos`, `rhel`, `centos` and other images.
|
|
|
|
```hcl
|
|
|
|
resource "google_compute_image" "cos-gvnic" {
|
|
project = "my-project"
|
|
name = "my-image"
|
|
source_image = "https://www.googleapis.com/compute/v1/projects/cos-cloud/global/images/cos-89-16108-534-18"
|
|
|
|
guest_os_features {
|
|
type = "GVNIC"
|
|
}
|
|
guest_os_features {
|
|
type = "SEV_CAPABLE"
|
|
}
|
|
guest_os_features {
|
|
type = "UEFI_COMPATIBLE"
|
|
}
|
|
guest_os_features {
|
|
type = "VIRTIO_SCSI_MULTIQUEUE"
|
|
}
|
|
}
|
|
|
|
module "vm-with-gvnic" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
boot_disk = {
|
|
initialize_params = {
|
|
image = google_compute_image.cos-gvnic.self_link
|
|
type = "pd-ssd"
|
|
}
|
|
}
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
nic_type = "GVNIC"
|
|
}]
|
|
service_account_create = true
|
|
}
|
|
# tftest modules=1 resources=3 inventory=gvnic.yaml
|
|
```
|
|
|
|
### Metadata
|
|
|
|
You can define labels and custom metadata values. Metadata can be leveraged, for example, to define a custom startup script.
|
|
|
|
```hcl
|
|
module "vm-metadata-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "nginx-server"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
labels = {
|
|
env = "dev"
|
|
system = "crm"
|
|
}
|
|
metadata = {
|
|
startup-script = <<-EOF
|
|
#! /bin/bash
|
|
apt-get update
|
|
apt-get install -y nginx
|
|
EOF
|
|
}
|
|
service_account_create = true
|
|
}
|
|
# tftest modules=1 resources=2 inventory=metadata.yaml
|
|
```
|
|
|
|
### IAM
|
|
|
|
Like most modules, you can assign IAM roles to the instance using the `iam` variable.
|
|
|
|
```hcl
|
|
module "vm-iam-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "webserver"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
iam = {
|
|
"roles/compute.instanceAdmin" = [
|
|
"group:webserver@example.com",
|
|
"group:admin@example.com"
|
|
]
|
|
}
|
|
}
|
|
# tftest modules=1 resources=2 inventory=iam.yaml
|
|
|
|
```
|
|
|
|
### Spot VM
|
|
|
|
[Spot VMs](https://cloud.google.com/compute/docs/instances/spot) are ephemeral compute instances suitable for batch jobs and fault-tolerant workloads. Spot VMs provide new features that [preemptible instances](https://cloud.google.com/compute/docs/instances/preemptible) do not support, such as the absence of a maximum runtime.
|
|
|
|
```hcl
|
|
module "spot-vm-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
options = {
|
|
spot = true
|
|
termination_action = "STOP"
|
|
}
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
}
|
|
# tftest modules=1 resources=1 inventory=spot.yaml
|
|
```
|
|
|
|
### Confidential compute
|
|
|
|
You can enable confidential compute with the `confidential_compute` variable, which can be used for standalone instances or for instance templates.
|
|
|
|
```hcl
|
|
module "vm-confidential-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "confidential-vm"
|
|
confidential_compute = true
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
|
|
}
|
|
|
|
module "template-confidential-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "confidential-template"
|
|
confidential_compute = true
|
|
create_template = true
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
}
|
|
|
|
# tftest modules=2 resources=2 inventory=confidential.yaml
|
|
```
|
|
|
|
### Disk encryption with Cloud KMS
|
|
|
|
This example shows how to control disk encryption via the the `encryption` variable, in this case the self link to a KMS CryptoKey that will be used to encrypt boot and attached disk. Managing the key with the `../kms` module is of course possible, but is not shown here.
|
|
|
|
```hcl
|
|
module "kms-vm-example" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = var.project_id
|
|
zone = "europe-west1-b"
|
|
name = "kms-test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
attached_disks = [{
|
|
name = "attached-disk"
|
|
size = 10
|
|
}]
|
|
service_account_create = true
|
|
encryption = {
|
|
encrypt_boot = true
|
|
kms_key_self_link = var.kms_key.self_link
|
|
}
|
|
}
|
|
# tftest modules=1 resources=3 inventory=cmek.yaml
|
|
```
|
|
|
|
### Instance template
|
|
|
|
This example shows how to use the module to manage an instance template that defines an additional attached disk for each instance, and overrides defaults for the boot disk image and service account.
|
|
|
|
```hcl
|
|
module "cos-test" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
boot_disk = {
|
|
initialize_params = {
|
|
image = "projects/cos-cloud/global/images/family/cos-stable"
|
|
}
|
|
}
|
|
attached_disks = [
|
|
{
|
|
name = "disk-1"
|
|
size = 10
|
|
}
|
|
]
|
|
service_account = "vm-default@my-project.iam.gserviceaccount.com"
|
|
create_template = true
|
|
}
|
|
# tftest modules=1 resources=1 inventory=template.yaml
|
|
```
|
|
|
|
### Instance group
|
|
|
|
If an instance group is needed when operating in instance mode, simply set the `group` variable to a non null map. The map can contain named port declarations, or be empty if named ports are not needed.
|
|
|
|
```hcl
|
|
locals {
|
|
cloud_config = "my cloud config"
|
|
}
|
|
|
|
module "instance-group" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "ilb-test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
boot_disk = {
|
|
image = "projects/cos-cloud/global/images/family/cos-stable"
|
|
}
|
|
service_account = var.service_account.email
|
|
service_account_scopes = ["https://www.googleapis.com/auth/cloud-platform"]
|
|
metadata = {
|
|
user-data = local.cloud_config
|
|
}
|
|
group = { named_ports = {} }
|
|
}
|
|
# tftest modules=1 resources=2 inventory=group.yaml
|
|
```
|
|
|
|
### Instance Schedule
|
|
|
|
Instance start and stop schedules can be defined via an existing or auto-created resource policy.
|
|
|
|
To use an existing policy pass its id to the `instance_schedule` variable:
|
|
|
|
```hcl
|
|
module "instance" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "schedule-test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
boot_disk = {
|
|
image = "projects/cos-cloud/global/images/family/cos-stable"
|
|
}
|
|
instance_schedule = {
|
|
resource_policy_id = "projects/my-project/regions/europe-west1/resourcePolicies/test"
|
|
}
|
|
}
|
|
# tftest modules=1 resources=1 inventory=instance-schedule-id.yaml
|
|
```
|
|
|
|
To create a new policy set its configuration in the `instance_schedule` variable. When removing the policy follow a two-step process by first setting `active = false` in the schedule configuration, which will unattach the policy, then removing the variable so the policy is destroyed.
|
|
|
|
```hcl
|
|
module "instance" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "schedule-test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
boot_disk = {
|
|
image = "projects/cos-cloud/global/images/family/cos-stable"
|
|
}
|
|
instance_schedule = {
|
|
create_config = {
|
|
vm_start = "0 8 * * *"
|
|
vm_stop = "0 17 * * *"
|
|
}
|
|
}
|
|
}
|
|
# tftest modules=1 resources=2 inventory=instance-schedule-create.yaml
|
|
```
|
|
|
|
### Snapshot Schedules
|
|
|
|
Snapshot policies can be attached to disks with optional creation managed by the module.
|
|
|
|
```hcl
|
|
module "instance" {
|
|
source = "./fabric/modules/compute-vm"
|
|
project_id = "my-project"
|
|
zone = "europe-west1-b"
|
|
name = "schedule-test"
|
|
network_interfaces = [{
|
|
network = var.vpc.self_link
|
|
subnetwork = var.subnet.self_link
|
|
}]
|
|
boot_disk = {
|
|
image = "projects/cos-cloud/global/images/family/cos-stable"
|
|
snapshot_schedule = "boot"
|
|
}
|
|
attached_disks = [
|
|
{
|
|
name = "disk-1"
|
|
size = 10
|
|
snapshot_schedule = "generic-vm"
|
|
}
|
|
]
|
|
snapshot_schedules = {
|
|
boot = {
|
|
schedule = {
|
|
daily = {
|
|
days_in_cycle = 1
|
|
start_time = "03:00"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
# tftest modules=1 resources=5 inventory=snapshot-schedule-create.yaml
|
|
```
|
|
<!-- BEGIN TFDOC -->
|
|
|
|
## Variables
|
|
|
|
| name | description | type | required | default |
|
|
|---|---|:---:|:---:|:---:|
|
|
| [name](variables.tf#L219) | Instance name. | <code>string</code> | ✓ | |
|
|
| [network_interfaces](variables.tf#L224) | Network interfaces configuration. Use self links for Shared VPC, set addresses to null if not needed. | <code title="list(object({ nat = optional(bool, false) network = string subnetwork = string addresses = optional(object({ internal = optional(string) external = optional(string) }), null) alias_ips = optional(map(string), {}) nic_type = optional(string) }))">list(object({…}))</code> | ✓ | |
|
|
| [project_id](variables.tf#L261) | Project id. | <code>string</code> | ✓ | |
|
|
| [zone](variables.tf#L363) | Compute zone. | <code>string</code> | ✓ | |
|
|
| [attached_disk_defaults](variables.tf#L17) | Defaults for attached disks options. | <code title="object({ auto_delete = optional(bool, false) mode = string replica_zone = string type = string })">object({…})</code> | | <code title="{ auto_delete = true mode = "READ_WRITE" replica_zone = null type = "pd-balanced" }">{…}</code> |
|
|
| [attached_disks](variables.tf#L38) | Additional disks, if options is null defaults will be used in its place. Source type is one of 'image' (zonal disks in vms and template), 'snapshot' (vm), 'existing', and null. | <code title="list(object({ name = string device_name = optional(string) size = string snapshot_schedule = optional(string) source = optional(string) source_type = optional(string) options = optional( object({ auto_delete = optional(bool, false) mode = optional(string, "READ_WRITE") replica_zone = optional(string) type = optional(string, "pd-balanced") }), { auto_delete = true mode = "READ_WRITE" replica_zone = null type = "pd-balanced" } ) }))">list(object({…}))</code> | | <code>[]</code> |
|
|
| [boot_disk](variables.tf#L83) | Boot disk properties. | <code title="object({ auto_delete = optional(bool, true) snapshot_schedule = optional(string) source = optional(string) initialize_params = optional(object({ image = optional(string, "projects/debian-cloud/global/images/family/debian-11") size = optional(number, 10) type = optional(string, "pd-balanced") })) })">object({…})</code> | | <code title="{ initialize_params = {} }">{…}</code> |
|
|
| [can_ip_forward](variables.tf#L101) | Enable IP forwarding. | <code>bool</code> | | <code>false</code> |
|
|
| [confidential_compute](variables.tf#L107) | Enable Confidential Compute for these instances. | <code>bool</code> | | <code>false</code> |
|
|
| [create_template](variables.tf#L113) | Create instance template instead of instances. | <code>bool</code> | | <code>false</code> |
|
|
| [description](variables.tf#L118) | Description of a Compute Instance. | <code>string</code> | | <code>"Managed by the compute-vm Terraform module."</code> |
|
|
| [enable_display](variables.tf#L124) | Enable virtual display on the instances. | <code>bool</code> | | <code>false</code> |
|
|
| [encryption](variables.tf#L130) | Encryption options. Only one of kms_key_self_link and disk_encryption_key_raw may be set. If needed, you can specify to encrypt or not the boot disk. | <code title="object({ encrypt_boot = optional(bool, false) disk_encryption_key_raw = optional(string) kms_key_self_link = optional(string) })">object({…})</code> | | <code>null</code> |
|
|
| [group](variables.tf#L140) | Define this variable to create an instance group for instances. Disabled for template use. | <code title="object({ named_ports = map(number) })">object({…})</code> | | <code>null</code> |
|
|
| [hostname](variables.tf#L148) | Instance FQDN name. | <code>string</code> | | <code>null</code> |
|
|
| [iam](variables.tf#L154) | IAM bindings in {ROLE => [MEMBERS]} format. | <code>map(list(string))</code> | | <code>{}</code> |
|
|
| [instance_schedule](variables.tf#L160) | Assign or create and assign an instance schedule policy. Either resource policy id or create_config must be specified if not null. Set active to null to dtach a policy from vm before destroying. | <code title="object({ resource_policy_id = optional(string) create_config = optional(object({ active = optional(bool, true) description = optional(string) expiration_time = optional(string) start_time = optional(string) timezone = optional(string, "UTC") vm_start = optional(string) vm_stop = optional(string) })) })">object({…})</code> | | <code>null</code> |
|
|
| [instance_type](variables.tf#L195) | Instance type. | <code>string</code> | | <code>"f1-micro"</code> |
|
|
| [labels](variables.tf#L201) | Instance labels. | <code>map(string)</code> | | <code>{}</code> |
|
|
| [metadata](variables.tf#L207) | Instance metadata. | <code>map(string)</code> | | <code>{}</code> |
|
|
| [min_cpu_platform](variables.tf#L213) | Minimum CPU platform. | <code>string</code> | | <code>null</code> |
|
|
| [options](variables.tf#L239) | Instance options. | <code title="object({ allow_stopping_for_update = optional(bool, true) deletion_protection = optional(bool, false) spot = optional(bool, false) termination_action = optional(string) })">object({…})</code> | | <code title="{ allow_stopping_for_update = true deletion_protection = false spot = false termination_action = null }">{…}</code> |
|
|
| [scratch_disks](variables.tf#L266) | Scratch disks configuration. | <code title="object({ count = number interface = string })">object({…})</code> | | <code title="{ count = 0 interface = "NVME" }">{…}</code> |
|
|
| [service_account](variables.tf#L278) | Service account email. Unused if service account is auto-created. | <code>string</code> | | <code>null</code> |
|
|
| [service_account_create](variables.tf#L284) | Auto-create service account. | <code>bool</code> | | <code>false</code> |
|
|
| [service_account_scopes](variables.tf#L292) | Scopes applied to service account. | <code>list(string)</code> | | <code>[]</code> |
|
|
| [shielded_config](variables.tf#L298) | Shielded VM configuration of the instances. | <code title="object({ enable_secure_boot = bool enable_vtpm = bool enable_integrity_monitoring = bool })">object({…})</code> | | <code>null</code> |
|
|
| [snapshot_schedules](variables.tf#L308) | Snapshot schedule resource policies that can be attached to disks. | <code title="map(object({ schedule = object({ daily = optional(object({ days_in_cycle = number start_time = string })) hourly = optional(object({ hours_in_cycle = number start_time = string })) weekly = optional(list(object({ day = string start_time = string }))) }) description = optional(string) retention_policy = optional(object({ max_retention_days = number on_source_disk_delete_keep = optional(bool) })) snapshot_properties = optional(object({ chain_name = optional(string) guest_flush = optional(bool) labels = optional(map(string)) storage_locations = optional(list(string)) })) }))">map(object({…}))</code> | | <code>{}</code> |
|
|
| [tag_bindings](variables.tf#L351) | Tag bindings for this instance, in key => tag value id format. | <code>map(string)</code> | | <code>null</code> |
|
|
| [tags](variables.tf#L357) | Instance network tags for firewall rule targets. | <code>list(string)</code> | | <code>[]</code> |
|
|
|
|
## Outputs
|
|
|
|
| name | description | sensitive |
|
|
|---|---|:---:|
|
|
| [external_ip](outputs.tf#L17) | Instance main interface external IP addresses. | |
|
|
| [group](outputs.tf#L26) | Instance group resource. | |
|
|
| [id](outputs.tf#L31) | Fully qualified instance id. | |
|
|
| [instance](outputs.tf#L36) | Instance resource. | |
|
|
| [internal_ip](outputs.tf#L41) | Instance main interface internal IP address. | |
|
|
| [internal_ips](outputs.tf#L49) | Instance interfaces internal IP addresses. | |
|
|
| [self_link](outputs.tf#L57) | Instance self links. | |
|
|
| [service_account](outputs.tf#L62) | Service account resource. | |
|
|
| [service_account_email](outputs.tf#L69) | Service account email. | |
|
|
| [service_account_iam_email](outputs.tf#L74) | Service account email. | |
|
|
| [template](outputs.tf#L82) | Template resource. | |
|
|
| [template_name](outputs.tf#L87) | Template name. | |
|
|
|
|
<!-- END TFDOC -->
|
|
## TODO
|
|
|
|
- [ ] add support for instance groups
|