Tags are key-value pairs attached to Cloud resources for organization and identification. Each tag consists of a key (like env) and a value (like production).
Add tags during resource creation or to existing resources. Tags are supported on Virtual Machines, Bare Metal servers, Volumes, Networks, Subnetworks, Load Balancers, Firewalls, Images, and File Shares.
During resource creation
-
Navigate to the resource creation page (for example, Cloud > Virtual Instances > Create Instance).
-
In the Additional options section, turn on the Add tags toggle.
-
Enter a Key and Value for each tag.
-
Click Add tag to add more tags if needed.
-
Complete the resource creation.
On existing resources
-
Open the resource details page (for example, Cloud > Networking > Load Balancers > select a Load Balancer).
-
Navigate to the Tags tab.
-
Turn on Add custom tags, then enter key-value pairs.
-
Click Save changes.
Include tags in the metadata field when creating or updating resources via the Gcore API:
{
"name": "my-instance",
"metadata": {
"env": "production",
"team": "backend"
}
}
metadata_map attribute when using the Gcore Terraform provider:
resource "gcore_instance" "example" {
name = "my-instance"
flavor_id = "g1-standard-2-4"
metadata_map = {
env = "production"
team = "backend"
}
}
| Parameter | Requirement |
|---|
| Key length | 3-255 characters |
| Value length | 3-255 characters |
| Forbidden characters | = in keys |
| Whitespace | Leading and trailing spaces are trimmed |
Tag keys cannot contain the = character.
Common tagging patterns
| Pattern | Example tags |
|---|
| Environment | env:production, env:staging, env:development |
| Service | service:authentication, service:payment |
| Ownership | team:backend, owner:devops |
| Cost tracking | cost-center:marketing, project:website-redesign |
- Calculate costs per environment (
env:production vs env:staging)
- Track spending by team or cost center
- Identify untagged resources that need classification
