RegionInstanceTemplate

Configure Nested Virtualisation and Simultaneous Hyper Threading on this VM. Structure is documented below

Whether to allow sending and receiving of packets with non-matching source or destination IPs. This defaults to false.

Enable Confidential Mode on this VM. Structure is documented below

Creation timestamp in RFC3339 text format.

A brief description of this resource.

Disks to attach to instances created from this template. This can be specified multiple times for multiple disks. Structure is documented below.

All of labels (key/value pairs) present on the resource in GCP, including the labels configured through Pulumi, other clients and services.

Enable Virtual Displays on this instance. Note: allow_stopping_for_update must be set to true in order to update this field.

List of the type and count of accelerator cards attached to the instance. Structure documented below.

A brief description to use for instances created from this template.

Action to be taken when a customer's encryption key is revoked. Supports STOP and NONE, with NONE being the default.

A set of key/value label pairs to assign to instances created from this template. Note: This field is non-authoritative, and will only manage the labels present in your configuration. Please refer to the field 'effective_labels' for all of the labels present on the resource.

The machine type to create. To create a machine with a custom type (such as extended memory), format the value like custom-VCPUS-MEM_IN_MB like custom-6-20480 for 6 vCPU and 20GB of RAM.

Metadata key/value pairs to make available from within instances created from this template.

The unique fingerprint of the metadata.

An alternative to using the startup-script metadata key, mostly to match the compute_instance resource. This replaces the startup-script metadata key on the created instance and thus the two mechanisms are not allowed to be used simultaneously.

Specifies a minimum CPU platform. Applicable values are the friendly names of CPU platforms, such as Intel Haswell or Intel Skylake. See the complete list here.

Creates a unique name beginning with the specified prefix. Conflicts with name. Max length is 54 characters. Prefixes with lengths longer than 37 characters will use a shortened UUID that will be more prone to collisions. Resulting name for a name_prefix<= 37 characters: name_prefix + YYYYmmddHHSSssss + 8 digit incremental counter Resulting name for a name_prefix 38 - 54 characters: name_prefix + YYmmdd + 3 digit incremental counter

Networks to attach to instances created from this template. This can be specified multiple times for multiple networks. Structure is documented below.

Configures network performance settings for the instance created from the template. Structure is documented below. Note: machine_type must be a supported type, the image used must include the GVNIC in guest-os-features, and network_interface.0.nic-type must be GVNIC in order for this setting to take effect.

Beta key/value pair represents partner metadata assigned to instance template where key represent a defined namespace and value is a json string represent the entries associted with the namespace.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

The combination of labels configured directly on the resource and default labels configured on the provider.

The Region in which the resource belongs. If region is not provided, the provider region is used.

Specifies the reservations that this instance can consume from. Structure is documented below.

A set of key/value resource manager tag pairs to bind to the instance. Keys must be in the format tagKeys/{tag_key_id}, and values are in the format tagValues/456.

The scheduling strategy to use. More details about this configuration option are detailed below.

The URI of the created resource.

Service account to attach to the instance. Structure is documented below.

Enable Shielded VM on this instance. Shielded VM provides verifiable integrity to prevent against malware and rootkits. Defaults to disabled. Structure is documented below. Note: shielded_instance_config can only be used with boot images with shielded vm support. See the complete list here.

Tags to attach to the instance.

The unique fingerprint of the tags.