CycleCloud will automatically create and add three tags to each node: a name, the cluster name, and the owner. These tags are meant to make it easier to audit ownership of the nodes when using non-CycleCloud tools. “Name” contains the full CycleCloud name of the node. “ClusterName” contains the name of the CycleCloud cluster the node is running in. Finally, “CycleOwner” contains information on which user started the node. CycleOwner uses this format: <username>@<site_name>:<site_id> where username is the CycleCloud user that started the node, site_name is the user defined name of the CycleCloud installation, and site_id is the CycleCloud Site ID that identifies the CycleCloud installation. For example, a cluster named “Demo” with a node called “master” started by “username” running on CycleCloud site “mysite” with id “92xy4vgh” would have the following tags created automatically:

Name => "Demo: master"
ClusterName => "Demo"
CycleOwner => "username@mysite:92xy4vgh"

If your cloud provider is AWS, you can also create additional tags to assign to the instance by specifying them with a node definition inside your template:

[cluster Demo]
  [[node master]]
    tags.Application = my application
    tags.CustomValue = 57
    tags.Custom Text = Hello world

Creating a node with this definition will result in three additional tags being set on the node:

Name => "Demo: master"
ClusterName => "Demo"
Application => "my application"
CustomValue => "57"
Custom Text => "Hello world"


Be aware this syntax will not work if your tag name includes quote marks or periods.

Tagging in Microsoft Azure

Tags in Azure work similar to tags in AWS. However, Azure tags are only supported by resources that support Resource Manager operations. If any resource created in Azure was done via the classic portal, tags cannot be used. Please see the Azure Resource Tag documentation for more information.

Tagging in Google Cloud

In Google Cloud, tags only apply to virtual machine instances. For additional information on tagging within Google Cloud, please refer to the documentation.