Skip to content

Commit c997ec4

Browse files
committed
docs: record where the default installer image moved on Talos v1.14
The upgrade flag's default is built from the image factory now, with the empty schematic pinned into the reference, where it used to be a plain ghcr.io tag. A mirror stocked only with ghcr.io will not serve it, and the pinned schematic fixes the extension set the default carries. The page already lists the other operator-visible v1.14 changes; this one was missing, and it is the one an airgapped operator runs into. Signed-off-by: Aleksei Sviridkin <[email protected]> Assisted-by: LLM
1 parent 3dff64c commit c997ec4

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

‎docs/operations/talosctl-commands.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,12 @@ Upstream dropped `--insecure` from `reset` in v1.14, so `talm reset --insecure`
4949

5050
Upstream changed the default: `talm support` now encrypts the generated bundle with age, to a built-in list of Sidero Labs recipients. `--no-encryption` turns that off, `--encryption-recipients` sends it to recipients you choose, and `--encryption-no-default-recipients` keeps yours while dropping theirs. Worth knowing before collecting a bundle from a cluster whose contents you would rather not hand to a third party, encrypted or otherwise.
5151

52+
## `talm upgrade` — the default installer image moved to the image factory on Talos v1.14
53+
54+
Upstream builds the `--image` default from the image factory now: `factory.talos.dev/metal-installer/376567988ad…:v1.14.0`, where the digest is the factory's empty schematic. It used to be `ghcr.io/siderolabs/installer:<version>`. Two things follow. The registry is different, so a mirror that only carries `ghcr.io` will not serve it. And the default now pins a schematic, so it ships the stock extension set rather than whatever a `ghcr.io` tag happened to hold.
55+
56+
This only bites a bare `talm upgrade` with neither `-f` nor `--image`. With `-f`, talm resolves the target from `values.yaml::image` at the project root and never consults the upstream default, which is the flow the presets are built around.
57+
5258
## `talm containers`, `logs`, `restart`, `stats` — `-k` / `--kubernetes` is deprecated
5359

5460
Upstream replaced the flag with `--namespace`, which takes `system`, `cri` or `taloscontainers`. The old spelling still works and prints `Flag --kubernetes has been deprecated, use --namespace cri instead`, so scripts keep running for now; move them over before the flag goes the way of the others on this page.

0 commit comments

Comments
 (0)