Tagging

​

Introduction

Tags are key-value labels you attach to resources in the ZEDEDA console. A tag consists of a key and a value separated by a colon, for example location:factory-A or env:production. Tags help you organize large fleets, filter list views, and scope role permissions to specific sets of projects. Tags are a cross-cutting feature: the same tagging model applies across nodes, applications, virtual networks, projects, and Kubernetes resources in Edge Infrastructure Services, as well as AI models in Edge Inference Services.

​

Tag Format

Enter each tag as key:value. The following rules apply:

• The key and value must each be at least 3 characters long.
• Alphanumeric characters, spaces, and most special characters are allowed. The characters <, >, %, &, ?, /, and \ are not allowed.
• Keys are case-insensitive. Values are case-sensitive.
• Each object does not allow duplicate keys.

Tags are displayed as pill-shaped labels in the console, with the key rendered in one color and the value in another.

​

Where Tags Apply

The following resource types support tags in Edge Infrastructure Services: Node network interfaces and IO adapters also support tags. See Interface tags and IO tags. In Edge Inference Services, AI model versions support version-level tags. See Version tags on AI models.

​

Tag Pool and Autocomplete

The console maintains a fleet-wide pool of existing tags for each resource type. When you add tags to an object, the tag input shows suggestions drawn from all tags already in use in your enterprise. Reusing tags from the pool keeps naming consistent across the fleet, which makes filtering and role scope more reliable.

​

Filter by Tag

Most list pages in Edge Infrastructure Services include a Tags filter in the filter panel. Selecting one or more tags narrows the list to objects that carry all selected tags. To filter a list by tag:

1. Open a supported list page such as Nodes, Applications, or Virtual Networks.
2. Open the filter panel.
3. Expand the Tags section.
4. Select one or more tags to apply.

Remove a tag from the filter to expand the results again.

​

Special Tag Uses

​

Interface tags

Network adapters on a node each support individual Interface Tags. Use them to label ports for organizing, searching, and filtering across your fleet — for example, to mark a port’s intended use or network segment. Interface Tags are descriptive and do not change how traffic is routed. Set Interface Tags in the Network Adapters tab on the node detail page (Infrastructure > Fleet > Nodes > [node] > Network Adapters). See Configure Node Adapters. When configuring a virtual network’s uplink, you can also select Port Tag Name as the binding method. In that mode, the virtual network attaches to whichever port on each node carries the matching Interface Tag. For example, tagging the WAN port on each node role:wan and setting the virtual network’s uplink to match role:wan lets a single project policy work across nodes with different physical port layouts, without hardcoding a port name.

​

IO tags

IO adapters (including USB controllers, GPUs, COM ports, and similar peripherals) support IO Tags. Use them to label individual hardware components for organizing, searching, and filtering — for example, type:inference-gpu or use:camera-usb. IO Tags are descriptive and do not change how adapters are assigned or used. Set IO Tags in the IO Adapters tab on the node detail page. See Configure Node Adapters.

​

Project tags and role scope

When creating or editing a role in Edge Infrastructure Services, you can define project tags in the Scope section. A role scoped to project tags applies only to projects whose tags match. Leaving the Scope section empty applies the role to all projects in the enterprise. For example, a role scoped to region:eu applies only to projects that carry that tag. This lets you grant different teams access to different subsets of the fleet without creating separate enterprises. See Permissions and Visibility and Manage Roles for more detail.

​

Marketplace edge app tags

In Marketplace > Edge Apps, you can filter the catalog by tag to find apps that carry specific key:value labels. Open the filter panel and expand the Tags section. Enter one or more tags in key:value format and press Enter after each one. The Marketplace queries the server for apps that match all entered tags and replaces the catalog list with the results. Remove a tag from the filter to expand the results again. The Tags filter is available in both the global catalog and the library view. It appears only when your connected backend supports tag-based queries for edge apps.

​

Version tags on AI models

In Edge Inference Services, individual model versions carry version-level tags. These tags encode training metadata such as the ML framework, the model author, and performance metrics. The model publishing workflow sets version tags; they appear on the model detail page.

​

Next Steps