Skip to content

docs: add details about template variables #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shoriminimoe merged 1 commit into from
Dec 30, 2025
Merged

docs: add details about template variables #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 15 additions & 3 deletions docs/spec/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down