-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove current APM soak infrastructure and decide on the next steps #14411
Comments
@lahsivjar please update this task with current status and either finish it if you have room or move it out of the iteration. |
The ADR is remaining, I will move this to the next iteration. |
Given the upcoming deadlines with HOtel, Azure and GCP I am not moving this to next iteration 106. Putting it in iteration 108 as I expect 107 to be also quite full. @lahsivjar @simitt let me know if this NEEDS to happen before, but is marked as low prio as of now. |
I don't see harm in moving to the next iteration. |
The current APM soak setup has not been working for a few months due to upgrade process being broken causing the clusters to be in a bad state. To fix this, the clusters will require to be recreated. In addition, now the clusters should be created as a team cluster rather than an individual cluster. We also need to take this opportunity to decide if we want to keep the soak testing active with the current state where the input data is not updated. Current soak testing infrastructure has 2 components:
Follow tasks are required:
The text was updated successfully, but these errors were encountered: