+`--update` can undo those pins. With `--force`, or when you accept its prompt for a file, it rewrites `Chart.yaml`, `values.yaml` and `templates/` from the preset without showing a diff; of `Chart.yaml` only the chart `name` survives, and its `version` is restamped to the talm release you ran. Every other key returns to the preset's value: the two version pins, `valueFiles`, the apply timeout, any pinned `certFingerprints`. A key the preset does not ship at all is dropped outright, `strictCharts` among them, so chart drift quietly goes back to being a warning. `values.yaml` is reset the same way: an empty `endpoint` fails the next render, while an empty `floatingIP` does not — the render simply comes out with no VIP, and a node file regenerated from it carries none either. `image` goes back to the installer the preset ships (`v1.12.6` in talm v0.35.0), also without an error or a warning, and `talm upgrade` takes its target from `values.yaml` unless you pass `--image`: if your nodes run a newer Talos than the preset, the next upgrade downgrades them. Put the pinned `image` back before that upgrade. Keep both files in git and diff them after every `--update`.
0 commit comments