+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.
0 commit comments