mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 04:33:36 +09:00
The migration procedure was headed "the order that avoids downtime" and closed by claiming step 3 is the only step that can refuse a connection. Step 1 restarts the instance: under cert-manager the CR gains serverCertSecretRef and serverCASecretRef, so the name of the Secret projected into the pods changes, and a pod-template change rolls the StatefulSet. The chart supports single-replica instances, and for those a rolling restart is plain downtime. The document already knew this in the other direction — the going-back section warns that deleting the Secret before the operator has reissued and rolled the StatefulSet leaves the next pod unable to start, and prints the rollout-status command — so the two halves contradicted each other. Both claims are now scoped to what they are true of: the order still matters, because it keeps enforcement behind the client migration, and step 3 remains the only step that refuses a client by policy rather than by restarting the server under it. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
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