mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-09 05:25:14 +09:00
Aleksei Sviridkin
45928d97fa
Bootstrap and control-plane providers built for the v1beta2 contract need Cluster API v1.11 or later. v1.13.7 is the newest release this cluster can move to from v1.10 in one step: upstream supports upgrades that skip at most three minor versions, so v1.14 has to follow in a later release. v1.13 still serves the v1beta1 API and accepts v1beta1-contract providers, so the providers that stay on that contract keep working; upstream stops serving v1beta1 in v1.16. The core package gains a components target in the style of the capmox and in-cluster IPAM packages: it downloads the release assets, checks them against pinned sums, applies patches/ and writes the YAML and the blob the chart mounts. The startupProbe that kept the manager alive through certificate provisioning becomes a patch instead of a hand edit of the vendored file, so a refresh carries it forward. The capmox and in-cluster IPAM pin comments named the v1.10.1 core as the reason to stay where they are. That no longer holds; the comments now give the reasons that do: the v1alpha2 API migration capmox v0.8 brings, and IPAM v1.1 moving to the v1beta2 contract while capmox v0.7 stays on v1beta1. The check that the core blob matches its YAML moves from its own bats file into the provider suite, so a failure now points at make components instead of a hand-run gzip that skips the sums and the patch. The vendored YAML carries patches/, so its sum cannot be pinned directly. The bats suite reverts the patches and checks the result against the pinned release sum instead, which catches a hand edit of the vendored file as well as a patch or a sum changed on its own. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>