mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-09 22:13:18 +09:00
Myasnikov Daniil
e4a9d433ae
A check against the code at v1.7.0-rc.3 and the upgrade-test records found statements the evidence does not support. talos.registryMirrors cannot be carried over from v1.6, which never had the key. Setting version: v7.3 does not end the refusal of a release whose cluster.version names 7.1. The lost migration log was one observation on a test cluster, not a property of the chart, which keeps the Job. The same check corrects narrower wording: the PostgreSQL restart was seen from v1.6.5 only and v1.6.0 shipped CloudNativePG 1.28.1; a disk added to spec.disks at v1.6.5 attaches only at the VM's next restart; the controller waits on Kube-OVN only on the isp-full variants; host is the node name; the API accepts a spec.cluster edit and the chart refuses it; the copy clone strategy is a CDI setting; and CRD validation ratcheting lets an unchanged dotted prefix through. The OpenSearch entry gains what a test cluster showed about the stale securityconfig-update Job of an instance created on v1.6.x: deleting it makes the operator recreate it on the platform's cluster domain. It stops short of a recovery, because whether the instance then finishes initializing was not confirmed. The release notes become the GitHub release body, so the three of these they repeat are corrected there too. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>