experiment: add rolling-update scenario
#687
Merged
Conversation
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.
What this PR does / why we need it:
This PR adds the
rolling-updateexperiment scenario. It is based on thebasicscenario but also triggers a rolling update twice (every 5 minutes).It should help evaluate the use of a
StatefulSetfor the sharded controller instead of aDeployment.The scenario already handles a fallback to the
StatefulSetif there is no webhosting-operatorDeployment.Which issue(s) this PR fixes:
Part of #672
Special notes for your reviewer:
Running the scenario shows the disruptive effects of a rolling update when using a
Deploymentfor the sharded controller: