Skip to content

Commit c9fcd29

Browse files
committed
docs(install): note the talm version pins on the update path
talm v0.35.0 no longer substitutes its built-in Kubernetes version for an empty templateOptions.kubernetesVersion. A project created before the cozystack preset pinned that key still renders, but without the component images talm used to generate, so each node follows the Kubernetes version of its own Talos release, with only a stderr warning to show it. The hard render error is reserved for contracts from Talos v1.14 on or an empty talosVersion, and the cozystack preset has pinned talosVersion below v1.14 since it was added, so a project from this guide gets the quiet outcome. The paragraph names both outcomes and says to pin kubernetesVersion in Chart.yaml. The update section already recommends `talm init --update`, which brings the preset's pins along, but once its Chart.yaml overwrite is accepted it replaces the whole file except `name` without showing what changed, so the paragraph says to compare and restore customized keys afterwards. Applied to every docs version whose page carries the update section. Signed-off-by: Aleksei Sviridkin <[email protected]> Assisted-by: LLM
1 parent 1d8749d commit c9fcd29

5 files changed

Lines changed: 10 additions & 0 deletions

File tree

‎content/en/docs/next/install/kubernetes/talm.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,8 @@ talm init --update --preset cozystack --force # non-interactive: auto-accept al
154154

155155
`--update` re-syncs the vendored `charts/talm/` exactly — files that the new library no longer ships (or strays like `.DS_Store`) are pruned — and advances the preset baseline in `.talm-preset.lock`.
156156

157+
talm v0.35.0 changes what an empty `templateOptions.kubernetesVersion` means. A project created before the preset pinned that key still renders while its `talosVersion` is v1.13 or older, but talm no longer fills in a Kubernetes version of its own: the component images it would have generated are dropped, so every node takes the Kubernetes version of the Talos release it happens to run, and talm prints a warning on stderr. With `talosVersion` v1.14 or later, or unset, the render stops with `templateOptions.kubernetesVersion is not set` instead. Either way, set `templateOptions.kubernetesVersion` in `Chart.yaml` to the version the cluster actually runs. `--update` can bring the preset's pins along too: with `--force`, or when you accept its `Chart.yaml` prompt, it replaces the whole file except `name` without showing what changed, so compare the result with your previous `Chart.yaml` (for example with `git diff`) and restore any keys you had customized, notably `talosVersion`, `kubernetesVersion` and `valueFiles`. [Talos versions and output format](https://talm.cozystack.io/configuration/talos-versions/) explains what each key selects.
158+
157159
#### Chart Drift Detection (Talm v0.32+)
158160

159161
Render commands read the project's local `charts/talm/` copy, never the binary's built-in charts, so upgrading the talm binary does not touch your project — the vendored chart silently goes stale. Release builds of talm detect this and print a non-fatal `WARN:` line on stderr for two independent signals:

‎content/en/docs/v1.3/install/kubernetes/talm.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,8 @@ talm init --update --preset cozystack # interactive: prompts for each p
151151
talm init --update --preset cozystack --force # non-interactive: auto-accept all diffs
152152
```
153153

154+
talm v0.35.0 changes what an empty `templateOptions.kubernetesVersion` means. A project created before the preset pinned that key still renders while its `talosVersion` is v1.13 or older, but talm no longer fills in a Kubernetes version of its own: the component images it would have generated are dropped, so every node takes the Kubernetes version of the Talos release it happens to run, and talm prints a warning on stderr. With `talosVersion` v1.14 or later, or unset, the render stops with `templateOptions.kubernetesVersion is not set` instead. Either way, set `templateOptions.kubernetesVersion` in `Chart.yaml` to the version the cluster actually runs. `--update` can bring the preset's pins along too: with `--force`, or when you accept its `Chart.yaml` prompt, it replaces the whole file except `name` without showing what changed, so compare the result with your previous `Chart.yaml` (for example with `git diff`) and restore any keys you had customized, notably `talosVersion`, `kubernetesVersion` and `valueFiles`. [Talos versions and output format](https://talm.cozystack.io/configuration/talos-versions/) explains what each key selects.
155+
154156
#### Encrypt / Decrypt Round-Trip
155157

156158
The encrypted copies are what you commit to git; the plaintext copies are what `talm` reads. Use these to round-trip between the two:

‎content/en/docs/v1.4/install/kubernetes/talm.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,8 @@ talm init --update --preset cozystack # interactive: prompts for each p
151151
talm init --update --preset cozystack --force # non-interactive: auto-accept all diffs
152152
```
153153

154+
talm v0.35.0 changes what an empty `templateOptions.kubernetesVersion` means. A project created before the preset pinned that key still renders while its `talosVersion` is v1.13 or older, but talm no longer fills in a Kubernetes version of its own: the component images it would have generated are dropped, so every node takes the Kubernetes version of the Talos release it happens to run, and talm prints a warning on stderr. With `talosVersion` v1.14 or later, or unset, the render stops with `templateOptions.kubernetesVersion is not set` instead. Either way, set `templateOptions.kubernetesVersion` in `Chart.yaml` to the version the cluster actually runs. `--update` can bring the preset's pins along too: with `--force`, or when you accept its `Chart.yaml` prompt, it replaces the whole file except `name` without showing what changed, so compare the result with your previous `Chart.yaml` (for example with `git diff`) and restore any keys you had customized, notably `talosVersion`, `kubernetesVersion` and `valueFiles`. [Talos versions and output format](https://talm.cozystack.io/configuration/talos-versions/) explains what each key selects.
155+
154156
#### Encrypt / Decrypt Round-Trip
155157

156158
The encrypted copies are what you commit to git; the plaintext copies are what `talm` reads. Use these to round-trip between the two:

‎content/en/docs/v1.5/install/kubernetes/talm.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,8 @@ talm init --update --preset cozystack # interactive: prompts for each p
151151
talm init --update --preset cozystack --force # non-interactive: auto-accept all diffs
152152
```
153153

154+
talm v0.35.0 changes what an empty `templateOptions.kubernetesVersion` means. A project created before the preset pinned that key still renders while its `talosVersion` is v1.13 or older, but talm no longer fills in a Kubernetes version of its own: the component images it would have generated are dropped, so every node takes the Kubernetes version of the Talos release it happens to run, and talm prints a warning on stderr. With `talosVersion` v1.14 or later, or unset, the render stops with `templateOptions.kubernetesVersion is not set` instead. Either way, set `templateOptions.kubernetesVersion` in `Chart.yaml` to the version the cluster actually runs. `--update` can bring the preset's pins along too: with `--force`, or when you accept its `Chart.yaml` prompt, it replaces the whole file except `name` without showing what changed, so compare the result with your previous `Chart.yaml` (for example with `git diff`) and restore any keys you had customized, notably `talosVersion`, `kubernetesVersion` and `valueFiles`. [Talos versions and output format](https://talm.cozystack.io/configuration/talos-versions/) explains what each key selects.
155+
154156
#### Encrypt / Decrypt Round-Trip
155157

156158
The encrypted copies are what you commit to git; the plaintext copies are what `talm` reads. Use these to round-trip between the two:

‎content/en/docs/v1.6/install/kubernetes/talm.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -154,6 +154,8 @@ talm init --update --preset cozystack --force # non-interactive: auto-accept al
154154

155155
`--update` re-syncs the vendored `charts/talm/` exactly — files that the new library no longer ships (or strays like `.DS_Store`) are pruned — and advances the preset baseline in `.talm-preset.lock`.
156156

157+
talm v0.35.0 changes what an empty `templateOptions.kubernetesVersion` means. A project created before the preset pinned that key still renders while its `talosVersion` is v1.13 or older, but talm no longer fills in a Kubernetes version of its own: the component images it would have generated are dropped, so every node takes the Kubernetes version of the Talos release it happens to run, and talm prints a warning on stderr. With `talosVersion` v1.14 or later, or unset, the render stops with `templateOptions.kubernetesVersion is not set` instead. Either way, set `templateOptions.kubernetesVersion` in `Chart.yaml` to the version the cluster actually runs. `--update` can bring the preset's pins along too: with `--force`, or when you accept its `Chart.yaml` prompt, it replaces the whole file except `name` without showing what changed, so compare the result with your previous `Chart.yaml` (for example with `git diff`) and restore any keys you had customized, notably `talosVersion`, `kubernetesVersion` and `valueFiles`. [Talos versions and output format](https://talm.cozystack.io/configuration/talos-versions/) explains what each key selects.
158+
157159
#### Chart Drift Detection (Talm v0.32+)
158160

159161
Render commands read the project's local `charts/talm/` copy, never the binary's built-in charts, so upgrading the talm binary does not touch your project — the vendored chart silently goes stale. Release builds of talm detect this and print a non-fatal `WARN:` line on stderr for two independent signals:

0 commit comments

Comments
 (0)