Repository navigation
fix(scout): one Scout pod at a time: Recreate strategy, bootstrap migration, SIGTERM drain - #571
Merged
Merged
Conversation
ebourgeois
force-pushed
the
scout-recreate-and-sigterm
branch
2 times, most recently
from
October 24, 2026 02:00
e109652 to
e1822c8
Compare
…ration, SIGTERM drain Scout upgrades ran the old and new pod side by side (RollingUpdate, no leader election) and both published; on kind a Service created mid-upgrade got records from both versions. The Scout Deployment now uses the Recreate strategy. bindy bootstrap scout merge-patches an existing Deployment to Recreate before its server-side apply, which the API server otherwise refuses while its defaulted rollingUpdate remains. Scout's source controllers drain on SIGTERM/SIGINT like the operator's, cutting the no-Scout gap per upgrade from the 30s grace period to under a second (measured on kind). ADR-0002 amended; migration guide, Scout guide, CALM and threat model v1.31 updated. Signed-off-by: Erick Bourgeois <erick@jeb.ca>
ebourgeois
force-pushed
the
scout-recreate-and-sigterm
branch
from
October 24, 2026 13:52
e1822c8 to
c4ab588
Compare
ebourgeois
added a commit
that referenced
this pull request
Oct 24, 2026
…IF upload (#572) The semgrep job had no job-level permissions, inherited the read-only floor from #490 and failed every scheduled run since 2026-09-10 on 'Resource not accessible by integration'. Also records the Cargo.lock refresh that #571 carried (ctutils 0.4.3 -> 0.4.5, RUSTSEC-2026-0385). Signed-off-by: Erick Bourgeois <erick@jeb.ca>
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
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.
Scout upgrades ran the old and new pod side by side (RollingUpdate, no leader election) and both published; on kind a Service created mid-upgrade got records from both versions. The Scout Deployment now uses the Recreate strategy. bindy bootstrap scout merge-patches an existing Deployment to Recreate before its server-side apply, which the API server otherwise refuses while its defaulted rollingUpdate remains. Scout's source controllers drain on SIGTERM/SIGINT like the operator's, cutting the no-Scout gap per upgrade from the 30s grace period to under a second (measured on kind).
ADR-0002 amended; migration guide, Scout guide, CALM and threat model v1.31 updated.
Signed-off-by: Erick Bourgeois erick@jeb.ca