younsl commented on PR #392: URL: https://github.com/apache/superset-kubernetes-operator/pull/392#issuecomment-6278272950
Thanks @villebro, agreed. Draining first means the snapshot matches exactly what migrate sees, with no writes landing after the dump. Plan: 1. Default backup.requiresDrain to true: drain, backup, then migrate/rotate. 2. On terminal backup failure (after retries), rehydrate components and remove the maintenance page. Migrate and rotate stay blocked. One question: rehydrate must use the image the schema still matches, not the new one. I'd recreate components pinned to status.lastLifecycleImage, which reuses the existing drain path. The alternative is scaling to zero instead of deleting during drain, so rehydrate restores the previous state as is. Which do you prefer? And should requiresDrain: false stay as an opt-out, or should I drop it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
