Instance templates in GCP - Mini Project: Build & Apply

Create a Google Cloud Instance Template

📖 Scenario: You are setting up a Google Cloud environment to launch virtual machines with consistent settings. To do this efficiently, you will create an instance template that defines the machine type, disk, and network settings. This template will help you launch multiple identical instances easily.

🎯 Goal: Build a Google Cloud instance template JSON configuration that specifies a machine type, boot disk image, and network interface.

📋 What You'll Learn

Create a JSON object named instanceTemplate with the required fields.

Specify the machine type as n1-standard-1.

Use the boot disk image projects/debian-cloud/global/images/family/debian-11.

Configure the network interface to use the default network.

Include a name field with the value my-instance-template.

💡 Why This Matters

🌍 Real World

Instance templates are used in Google Cloud to create VM instances with consistent settings quickly and reliably.

💼 Career

Understanding instance templates is essential for cloud engineers and architects managing scalable and repeatable infrastructure deployments.

1

Create the base instance template object

Create a JSON object called instanceTemplate with a name field set to "my-instance-template".

GCP

{
  "name": "my-instance-template"
  // Your code here
}

Hint

Start by defining the name property inside the JSON object.

2

Add the machine type configuration

Add a properties object inside instanceTemplate with a machineType field set to "n1-standard-1".

GCP

{
  "name": "my-instance-template",
  "properties": {
    "machineType": "n1-standard-1"
    // Your code here
  }
}

Hint

Inside properties, set the machineType to "n1-standard-1".

3

Add boot disk configuration

Inside properties, add a disks array with one object. This object must have boot set to true, autoDelete set to true, and a initializeParams object with sourceImage set to "projects/debian-cloud/global/images/family/debian-11".

GCP

{
  "name": "my-instance-template",
  "properties": {
    "machineType": "n1-standard-1",
    "disks": [
      {
        "boot": true,
        "autoDelete": true,
        "initializeParams": {
          "sourceImage": "projects/debian-cloud/global/images/family/debian-11"
        }
      }
    ]
    // Your code here
  }
}

Hint

Define the boot disk inside the disks array with the required fields.

4

Add network interface configuration

Inside properties, add a networkInterfaces array with one object that has a network field set to "global/networks/default".

GCP

{
  "name": "my-instance-template",
  "properties": {
    "machineType": "n1-standard-1",
    "disks": [
      {
        "boot": true,
        "autoDelete": true,
        "initializeParams": {
          "sourceImage": "projects/debian-cloud/global/images/family/debian-11"
        }
      }
    ],
    "networkInterfaces": [
      {
        "network": "global/networks/default"
      }
    ]
    // Your code here
  }
}

Hint

Add the network interface configuration inside properties to connect to the default network.

Practice

1. What is the main purpose of an instance template in Google Cloud Platform?

easy

A. To store data permanently for virtual machines

B. To manage user access to virtual machines

C. To monitor the performance of virtual machines

D. To save VM configuration settings for creating identical instances quickly

Solution

1. Step 1: Understand what instance templates store

   Instance templates save the configuration details like machine type, disk image, and network settings.

2. Step 2: Identify their main use

   They allow quick creation of many identical VM instances without repeating setup.

3. Final Answer:

   To save VM configuration settings for creating identical instances quickly -> Option D

4. Quick Check:

   Instance templates = VM settings saved [OK]

Hint: Instance templates store VM setup for easy reuse [OK]

Common Mistakes:

• Confusing instance templates with storage or monitoring
• Thinking instance templates manage user permissions
• Assuming instance templates hold data permanently

2. Which of the following is the correct gcloud command to create an instance template named web-template with machine type e2-medium?

easy

A. gcloud compute instance-templates new web-template --type=e2-medium

B. gcloud compute instance-templates create web-template --machine-type=e2-medium

C. gcloud compute instances create web-template --machine-type=e2-medium

D. gcloud create instance-template web-template --machine e2-medium

Solution

1. Step 1: Identify the correct gcloud command for instance templates

   The command to create instance templates starts with gcloud compute instance-templates create.

2. Step 2: Check the machine type flag

   The correct flag is --machine-type= followed by the machine type.

3. Final Answer:

   gcloud compute instance-templates create web-template --machine-type=e2-medium -> Option B

4. Quick Check:

   Correct command syntax = gcloud compute instance-templates create web-template --machine-type=e2-medium [OK]

Hint: Use 'instance-templates create' with '--machine-type' flag [OK]

Common Mistakes:

• Using 'instances create' instead of 'instance-templates create'
• Wrong flag names like '--machine' or '--type'
• Incorrect command order or missing 'compute'

3. Given this snippet:

gcloud compute instance-templates create my-template \
  --machine-type=n1-standard-1 \
  --image-family=debian-11 \
  --image-project=debian-cloud

What will be the machine type of instances created from my-template?

medium

A. debian-11

B. e2-medium

C. n1-standard-1

D. debian-cloud

Solution

1. Step 1: Identify the machine type flag in the command

   The flag --machine-type=n1-standard-1 sets the machine type.

2. Step 2: Understand other flags

   --image-family and --image-project specify the OS image, not machine type.

3. Final Answer:

   n1-standard-1 -> Option C

4. Quick Check:

   Machine type flag sets instance type [OK]

Hint: Look for '--machine-type' flag for VM size [OK]

Common Mistakes:

• Confusing image family with machine type
• Choosing project name as machine type
• Ignoring the '--machine-type' flag

4. You tried to create an instance template with this command:

gcloud compute instance-templates create test-template --machine-type e2-small

But it failed. What is the likely error?

medium

A. Missing image or boot disk specification

B. Instance template name 'test-template' is invalid

C. Machine type 'e2-small' does not exist

D. Command should be 'gcloud create instance-template'

Solution

1. Step 1: Check required arguments for instance-templates create

   Instance templates require a machine type AND a boot disk specification (e.g., --image-family and --image-project).

2. Step 2: Validate other parts

   The instance template name and machine type are valid, and the command starts correctly with gcloud compute instance-templates create. Flag syntax with space is accepted.

3. Final Answer:

   Missing image or boot disk specification -> Option A

4. Quick Check:

   Instance templates need image spec [OK]

Hint: Include --image-family & --image-project flags [OK]

Common Mistakes:

• Forgetting to specify image or boot disk flags
• Wrong command order or missing 'compute'
• Assuming machine type is invalid without checking

5. You want to create a managed instance group that automatically updates all VMs when the instance template changes. Which approach should you use?

hard

A. Create a managed instance group with the instance template and enable rolling updates

B. Manually delete and recreate each VM after changing the template

C. Use an unmanaged instance group with the new template

D. Create a new instance template but keep the old managed group unchanged

Solution

1. Step 1: Understand managed instance groups and updates

   Managed instance groups can use instance templates and support rolling updates to replace VMs smoothly.

2. Step 2: Identify the best method for automatic updates

   Enabling rolling updates on the managed group with the new template applies changes automatically.

3. Final Answer:

   Create a managed instance group with the instance template and enable rolling updates -> Option A

4. Quick Check:

   Managed groups + rolling updates = automatic VM updates [OK]

Hint: Use managed groups with rolling updates for auto changes [OK]

Common Mistakes:

• Thinking unmanaged groups support automatic updates
• Manually recreating VMs instead of using rolling updates
• Ignoring instance template updates in managed groups