Andrey Smirnov 7bb205ebe2

fix: don't use runtime-specs Mount struct in machine config ...

First of all, it breaks our backwards compatibility promises and breaks
documentation generation. Upstream `specs.Mount` might change at any
time.

The issue was that containerd 1.7.x brings in new `specs.Mount` which
contains extra fields which don't have `omitempty` for YAML, so
machinery always generates them which confuses old Talos versions.

Use a copy of the upstream struct with proper YAML tags, and also
provide a special trick to make sure if the upstream struct changes, we
have a chance to update our copy of the struct.

Also this fixes docs and JSON schema.

Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>

2023-10-11 23:06:19 +04:00

..

_index.md

docs: fork docs for Talos 1.6

2023-08-17 19:37:38 +04:00

api.md

feat: update containerd to 1.7.x

2023-09-28 16:33:57 +04:00

cli.md

feat: update Kubernetes to 1.29.0-alpha.1

2023-09-26 17:30:52 +04:00

configuration.md

fix: don't use runtime-specs Mount struct in machine config

2023-10-11 23:06:19 +04:00

kernel.md

docs: fork docs for Talos 1.6

2023-08-17 19:37:38 +04:00