Problem
Machine configs generated by Omni stay pinned to the version contract of the Talos version the cluster was created with. Clusters upgraded over time keep old-format configs indefinitely: features that depend on newer config formats (e.g. multi-doc discovery service configuration) remain unavailable, and long-lived fleets accumulate legacy config shapes.
What
A user-initiated way to bump a cluster's machine config version contract. Direction from planning discussion: on bump, Omni regenerates the base config at the new contract; config patches that conflict with or are invalid under the new contract must be fixed by the user, with Talos rejecting invalid configs so the cluster stays healthy on its current config until patches are resolved — no silent breakage.
Open design question: bump first and fix patches reactively, or prepare and verify a migration before bumping the contract.
Why
- Features gated on newer config formats are inaccessible to long-lived clusters
- The same modernization story applies to Terraform-provider users following reproducible config generation outside Omni
- Reduces long-tail support burden from legacy configs
Problem
Machine configs generated by Omni stay pinned to the version contract of the Talos version the cluster was created with. Clusters upgraded over time keep old-format configs indefinitely: features that depend on newer config formats (e.g. multi-doc discovery service configuration) remain unavailable, and long-lived fleets accumulate legacy config shapes.
What
A user-initiated way to bump a cluster's machine config version contract. Direction from planning discussion: on bump, Omni regenerates the base config at the new contract; config patches that conflict with or are invalid under the new contract must be fixed by the user, with Talos rejecting invalid configs so the cluster stays healthy on its current config until patches are resolved — no silent breakage.
Open design question: bump first and fix patches reactively, or prepare and verify a migration before bumping the contract.
Why