mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-10 06:24:09 +09:00
The guard's refusal message told the operator to run the platform migration, but the case that reaches it is precisely one the migration already ran and stamped for (its slot was renumbered out on a backport, or the parent HelmRelease predates the application.kind label and the selector skipped it) -- re-running does nothing. Name the manual recovery instead: annotate resource-policy=keep on the listed MachineDeployments, then stamp the cozystack-version ConfigMap back below the worker-adoption migration so it re-runs. Also note in the Phase 2 README that computeplane clusters render their worker pools as separate KubernetesNodes releases too. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
How to test packages local
cd packages/core/installer
make image-cozystack REGISTRY=YOUR_CUSTOM_REGISTRY
make apply
kubectl delete po -l app=source-controller -n cozy-fluxcd