Resource naming and labels in GCP - Commands & Configuration

Introduction

When you create resources in Google Cloud, you need to give them names and labels. Names identify each resource uniquely. Labels help organize and find resources easily later.

When you want to keep track of which project or team owns a resource.

When you need to filter resources by environment like development or production.

When you want to group resources by application or service.

When you want to apply billing or cost tracking to specific groups of resources.

When you want to quickly find resources using the Google Cloud Console or CLI.

Commands

This command creates a virtual machine named 'example-instance' in the specified zone. It adds labels 'env=dev' and 'team=analytics' to help organize and identify the instance.

Terminal

gcloud compute instances create example-instance --zone=us-central1-a --labels=env=dev,team=analytics

Expected Output

Created [https://www.googleapis.com/compute/v1/projects/my-project/zones/us-central1-a/instances/example-instance].

NAME               ZONE           MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP     STATUS

example-instance    us-central1-a  e2-medium                   10.128.0.5   34.68.123.45    RUNNING

→

--labels - Assigns key=value pairs to the resource for organization

→

--zone - Specifies the location where the resource is created

This command shows the labels assigned to the 'example-instance' VM in JSON format so you can verify them.

Terminal

gcloud compute instances describe example-instance --zone=us-central1-a --format=json(labels)

Expected Output

{

  "labels": {

    "env": "dev",

    "team": "analytics"

  }

}

→

--format - Formats the output to show only labels in JSON

This command adds a new label 'priority=high' to the existing labels on the 'example-instance' VM.

Terminal

gcloud compute instances add-labels example-instance --zone=us-central1-a --labels=priority=high

Expected Output

Updated [https://www.googleapis.com/compute/v1/projects/my-project/zones/us-central1-a/instances/example-instance].

→

--labels - Adds or updates labels on the resource

Verify that the new label 'priority=high' was added successfully.

Terminal

gcloud compute instances describe example-instance --zone=us-central1-a --format=json(labels)

Expected Output

{

  "labels": {

    "env": "dev",

    "priority": "high",

    "team": "analytics"

  }

}

→

--format - Formats output to show labels in JSON

Key Concept

If you remember nothing else from this pattern, remember: use clear, consistent names and labels to organize and find your cloud resources easily.

Common Mistakes

Using spaces or uppercase letters in resource names

Resource names must be lowercase and cannot contain spaces, or the creation will fail.

Use only lowercase letters, numbers, and hyphens in names.

Assigning labels with invalid characters or too long keys

Labels must follow specific rules: keys and values can only have lowercase letters, numbers, underscores, and dashes, and keys must be 63 characters or less.

Follow GCP label naming rules strictly to avoid errors.

Not using labels at all

Without labels, it becomes hard to filter, group, or track resources, especially in large projects.

Always add meaningful labels like environment, team, or application.

Summary

Create resources with clear, lowercase names following GCP rules.

Use labels as key=value pairs to organize and filter resources.

Verify labels with describe commands and update them as needed.

Practice

1. What is the main purpose of labels in Google Cloud Platform (GCP)?

easy

A. To organize and filter cloud resources using key-value pairs

B. To set the resource's IP address

C. To define the resource's billing account

D. To encrypt the resource data

Solution

1. Step 1: Understand what labels do in GCP

   Labels are simple key-value pairs attached to resources to help organize and filter them easily.

2. Step 2: Compare options with label purpose

   Only To organize and filter cloud resources using key-value pairs correctly describes labels as tools for organization and filtering.

3. Final Answer:

   To organize and filter cloud resources using key-value pairs -> Option A

4. Quick Check:

   Labels = Organize and filter resources [OK]

Hint: Labels are for organizing and filtering resources [OK]

Common Mistakes:

• Confusing labels with IP or billing settings
• Thinking labels encrypt data
• Assuming labels set resource addresses

2. Which of the following is a valid resource name in GCP?

easy

A. my-instance-01

B. My_Instance_01

C. instance@01

D. instance 01

Solution

1. Step 1: Recall GCP resource naming rules

   Resource names must be lowercase letters, numbers, and hyphens only, no spaces or special characters.

2. Step 2: Check each option

   my-instance-01 uses lowercase letters, numbers, and hyphens correctly. Options A, B, and C contain uppercase letters, spaces, special characters, or underscores, which are invalid.

3. Final Answer:

   my-instance-01 -> Option A

4. Quick Check:

   Valid names use lowercase, numbers, hyphens only [OK]

Hint: Valid names use only lowercase letters, numbers, and hyphens [OK]

Common Mistakes:

• Using uppercase letters in names
• Including spaces or special characters
• Using underscores instead of hyphens

3. Given these labels on a VM instance: {"env":"prod", "team":"alpha", "priority":"high"}, which filter will correctly select this instance?

medium

A. labels.env = "dev" OR labels.priority = "low"

B. labels.priority = "medium"

C. labels.team = "beta"

D. labels.env = "prod" AND labels.team = "alpha"

Solution

1. Step 1: Understand the instance's labels

   The instance has labels: env=prod, team=alpha, priority=high.

2. Step 2: Evaluate each filter

   labels.env = "prod" AND labels.team = "alpha" matches env=prod and team=alpha, so it selects the instance. Options A, C, and D do not match the instance's labels.

3. Final Answer:

   labels.env = "prod" AND labels.team = "alpha" -> Option D

4. Quick Check:

   Filter matches labels exactly [OK]

Hint: Match filter keys and values exactly to labels [OK]

Common Mistakes:

• Using wrong label keys or values
• Mixing AND/OR incorrectly
• Assuming partial matches select resource

4. You try to create a GCP resource with the name my_resource_01 but get an error. What is the likely cause?

medium

A. Resource names cannot start with a letter

B. Underscores are not allowed in resource names

C. Resource names must be uppercase

D. Resource names must contain spaces

Solution

1. Step 1: Recall resource naming restrictions

   GCP resource names allow only lowercase letters, numbers, and hyphens. Underscores are not allowed.

2. Step 2: Analyze the given name

   The name contains underscores, which violates the naming rules, causing the error.

3. Final Answer:

   Underscores are not allowed in resource names -> Option B

4. Quick Check:

   Underscores invalid in names [OK]

Hint: Avoid underscores; use hyphens instead [OK]

Common Mistakes:

• Thinking uppercase letters are required
• Assuming names must start with numbers
• Believing spaces are allowed

5. You want to organize your GCP resources by environment and project. Which is the best way to do this using naming and labels?

hard

A. Use labels only for billing, not for environment or project

B. Use random resource names and no labels

C. Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"}

D. Use resource names with spaces and no labels

Solution

1. Step 1: Understand best practices for naming and labeling

   Resource names should be descriptive and labels should add metadata for filtering and organization.

2. Step 2: Evaluate options for organizing by environment and project

   Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"} uses clear naming and labels for environment and project, making management easy. Other options ignore labels or use invalid names.

3. Final Answer:

   Use resource names like prod-db-01 and labels {"env":"prod", "project":"sales"} -> Option C

4. Quick Check:

   Descriptive names + labels = best organization [OK]

Hint: Combine clear names with labels for best organization [OK]

Common Mistakes:

• Ignoring labels for organization
• Using invalid characters in names
• Not linking names and labels logically