User Tools

Site Tools


zededa:tagging

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
zededa:tagging [2026/06/28 18:20] – created mczededa:tagging [2026/08/11 12:14] (current) – old revision restored (2026/06/28 20:01) mc
Line 53: Line 53:
  
 Note: the public documentation states that node tags are "matched" to application/deployment tags but does not spell out the exact boolean semantics (whether a node must carry all of an application's tags, a subset, or exactly one). Treat the match as tag-based association scoped to a project and confirm the precise operator against controller behavior before relying on subset/superset assumptions. Note: the public documentation states that node tags are "matched" to application/deployment tags but does not spell out the exact boolean semantics (whether a node must carry all of an application's tags, a subset, or exactly one). Treat the match as tag-based association scoped to a project and confirm the precise operator against controller behavior before relying on subset/superset assumptions.
 +
  
 ==== Cluster and network-instance selection by tag ==== ==== Cluster and network-instance selection by tag ====
Line 58: Line 59:
   * When adding nodes to an Edge Kubernetes Service cluster in the GUI, you supply existing **Edge Node Tags** and existing **Edge Node Network Adapter Tags** to pick the nodes and the adapters used for cluster routing.   * When adding nodes to an Edge Kubernetes Service cluster in the GUI, you supply existing **Edge Node Tags** and existing **Edge Node Network Adapter Tags** to pick the nodes and the adapters used for cluster routing.
   * For the cluster network, choosing **Tag** (instead of Default) means you specify a tag that must match the tag used when creating the switch network instances on the nodes. Network instances carrying that tag are picked up on all cluster nodes to form the cluster network.   * For the cluster network, choosing **Tag** (instead of Default) means you specify a tag that must match the tag used when creating the switch network instances on the nodes. Network instances carrying that tag are picked up on all cluster nodes to form the cluster network.
 +
 +{{ :zededa_cluster_network_by_tag.svg | Switch NI tag → cluster network}}
 +
   * Adapter labels (shared labels) let you assign a free-form string to one or more ports so a network instance can target a group of ports; a port can carry multiple labels and belong to multiple groups.   * Adapter labels (shared labels) let you assign a free-form string to one or more ports so a network instance can target a group of ports; a port can carry multiple labels and belong to multiple groups.
  
 +**For non-clustered - EVE-KVM based edge nodes**
 +
 +{{ :zededa_ni_tag_evekvm.svg |Adapter label → network instance → VM (EVE-KVM)}}
 ===== Tags in the API ===== ===== Tags in the API =====
  
Line 99: Line 106:
 The ''zededa/zedcloud'' provider authenticates with a ZEDEDA Cloud API token and exposes tags as an HCL ''map(string)''. The ''zededa/zedcloud'' provider authenticates with a ZEDEDA Cloud API token and exposes tags as an HCL ''map(string)''.
  
-==== Provider setup ==== 
- 
-<code> 
-terraform { 
-  required_providers { 
-    zedcloud = { 
-      source  = "zededa/zedcloud" 
-      version = "2.4.0" 
-    } 
-  } 
-} 
- 
-provider "zedcloud" { 
-  zedcloud_url   = "https://zedcontrol.zededa.net" 
-  zedcloud_token = var.zedcloud_token 
-} 
-</code> 
  
 ==== Object tags on resources ==== ==== Object tags on resources ====
zededa/tagging.1782670818.txt.gz · Last modified: by mc