From 47bd609d26e9adf3372ef43be283696206787377 Mon Sep 17 00:00:00 2001 From: Sam Caldwell Date: Tue, 30 Dec 2025 10:41:56 -0700 Subject: [PATCH] docs: add details about template variables --- docs/spec/overview.md | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/docs/spec/overview.md b/docs/spec/overview.md index 713dcb6..6e2597c 100644 --- a/docs/spec/overview.md +++ b/docs/spec/overview.md @@ -107,13 +107,25 @@ capacity: 107374182400 # 100 GB ### Template Variables -Dynamic values using template syntax: +> [!NOTE] +> The template variable names and syntax are an experimental feature and subject to change. + +Fleet Manager supports the following dynamic values: +- `clusterName`: the name of the target cluster +- `clusterId`: the ID of the target cluster + +Values can be included in the manifest using the following template syntax: ```yaml -metadata: - name: "app-{{ cluster_name }}" +resources: + - type: virdomain + name: "vm-{{ clusterName }}" + description: "This VM is on cluster_name={{clusterName}} cluster_id={{clusterId}}" ``` +> [!TIP] +> Kraken uses the application `metadata.name` field to uniquely identify applications. Due to this behavior, it is recommended to use dynamic values in resource definitions only and not in application metadata to avoid creating duplicate applications. + ## Validation Rules ### Naming Conventions