prod: bump argocd dex memory limit to match staging #1896
Closed
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
The argocd-dex-server is continually crashing and restarting with error 139 in production. There are a lot of logs coming form this pod that may be related to this. Unfortunately it had less memory request and limit than staging This patch hopes to resolve the crashing issue but also to correct the discrepancy that staging has more resources than production; this should probably never happen. Bug: T380029
deer-wmde
approved these changes
Dec 11, 2024
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.
The argocd-dex-server is continually crashing and restarting with error 139 in production. There are a lot of logs coming from this pod that may be related to this.
Unfortunately it had less memory request and limit than staging
This patch hopes to resolve the crashing issue but also to correct the discrepancy that staging has more resources than production; this should probably never happen.
Bug: T380029