Rolling update fixes with internal state - #1080
Merged
stgraber merged 9 commits intoSep 16, 2026
Merged
Conversation
breml
force-pushed
the
rolling-update-fixes-with-internal-state
branch
2 times, most recently
from
September 14, 2026 13:46
1d67501 to
781c336
Compare
breml
force-pushed
the
rolling-update-fixes-with-internal-state
branch
4 times, most recently
from
September 15, 2026 09:52
babad48 to
1484384
Compare
breml
marked this pull request as ready for review
September 15, 2026 10:53
Closed
Member
|
@breml needs a rebase |
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Replace the previous in memory, volatile server update state with an internal state persisted in the DB, which allows for a more robust and failure tolerant handling in the cluster rolling update state machine. Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
…pdate additionally centralize the definition of the states, timeouts and retry definitions in the rollingUpdateStateDefinition map, which drives the rolling update and restart operations. Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
Signed-off-by: Lucas Bremgartner <lucas.bremgartner@futurfusion.io>
breml
force-pushed
the
rolling-update-fixes-with-internal-state
branch
from
September 16, 2026 05:40
1484384 to
0c7c5e8
Compare
Member
Author
done |
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
2 participants
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.
Replace the previous in memory, volatile server update state with an internal state persisted in the DB, which allows for a more robust and failure tolerant handling in the cluster rolling update state machine.
Additionally centralize the definition of the states, timeouts and retry definitions in the
rollingUpdateStateDefinitionmap, which drives the rolling update and restart operations. This aligns the definition of the state machine a bit closer with the state machine used for the automated deployment.Since the state is now in the DB, this also improves the situation for the future use of cowsql, since the (now no longer volatile) server state is also in the DB.