[Bugfix] Make user simulator a CronJob #29
Merged
Conversation
This file contains 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
…every 3 minutes * This should fix the OOMKills, as the pods are only active for a short time and scheduling is performed by K8s
* Removed unneeded dependencies
…rfile * Update and improve documentation
|
FYI chose to use GitMoji for the commit messages, I think it could make it a lot easier spotting the intention of a commit if we make it required for the future, also including the service that the commit affects. |
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.
Fixes #28.
This PR changes the benign load generation approach, by making the
user-simulatorpod run as a CronJob once every 3 minutes.This change should lead to no more OOMKills of the
user-simulatoron the K8s side.