feat(deploy): add recreate deploy strategy [SLIP-71]#17
Merged
Conversation
Add 'recreate' strategy (stop-old → start-new → health-check → route-update) as alternative to blue-green. Old container is stopped but not removed until new passes health check, enabling fast rollback via restart. - RuntimeBackend trait: add start_container(), stop_container(), inspect_container_port() - DeployStatus: add StoppingOld, RemovingRoute, RestartingOld + rollback_failed field - 3-tier rollback: restart old → recreate from previous_tag → alert - Strategy validation: accept 'blue-green' and 'recreate' only - drain_timeout warned (not errored) for recreate - Works for both container and pod deploys
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add recreate deploy strategy (stop-old → start-new → health-check → route-update) as alternative to blue-green.
SLIP-71