Add chaos experiment scenario
#648
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
The memory usage is much higher during sharder resyncs now that they run with parallelism.
github-project-automation
bot
moved this from In progress
to Done
in kubernetes-controller-sharding
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 another scenario to the
experimenttool:chaos.The scenario runs for 15 minutes, creates about 4.5k
Websites, and terminates a random shard every 5 minutes.Which issue(s) this PR fixes:
Fixes n/a
Special notes for your reviewer:
With #647, I can run load test experiments on my shoot cluster reliably again.
The
chaosscenario reveals that it's hard to fulfill the P99 SLOs in a 15-minute time frame with multiple shard terminations. This will be even harder when performing a rolling update.However, the results also show that the P99 SLI on a 1-minute time frame recovers quickly (~2m), now that the sharder performs drain/move operations concurrently (see #637).
P99 is not met:
P95 is met:
