Repository navigation
Test rollouts of the current chart instead of upgrades from the previous one - #40
Merged
Merged
Conversation
…ious one Weir has no users to stay compatible with. The kind test now rolls this checkout's chart out under load from one current-SDK soak client, instead of upgrading from the previous server's chart through the base commit with clients of two SDKs. The soak client moves to weir-tests c992d6f, which uses weir-go v0.24.1.
df28116 is weir-tests main with klauspost/compress v1.20.2; the SDK stays v0.24.1. Also correct the script header: the three replicas roll out twice.
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.
Weir has no users yet, so the chart no longer needs to prove that a release upgrades from the previous server's chart while clients of the previous SDK keep running. The kind test now rolls this checkout's chart out under load from one current-SDK soak client: twice at one replica, through a replacement that starts late, up to three replicas, twice at three, and back down. Rollouts still replace every Pod, so drain and replacement-first behaviour keep their coverage, while the history walk, the base-commit chart, the second SDK build and the cross-repository pin checks go away. The configuration guide also drops its advice to upgrade servers before clients.
The soak client is now installed from weir-tests df28116 (weir-go v0.24.1, klauspost/compress v1.20.2) instead of 1347bcd (v0.23.0), and the docs move the client SDK to v0.24.1 to match. The job is renamed from
upgradetorollout, so the branch protection's required check changes with it. The new script passed locally in kind on arm64 and in CI, with no caller errors and no outcome violations.