This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Aerogear 10281 sop restart #99
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
The current SOP instructs troubleshooters to scale pods during periods of memory pressure. This is incorrect the the affected pod should be restarted.
What
The SOP removed the instructions to scale the pod and replaced them with instructions to rebstart the pod based on the AMQ SOP
Why
UPS is not scalable and the instructions were wrong and not helpful.
Verification Steps
Docs only, no technical verification.