Bump production Jenkins deployment resources #204
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
These options are set under `controller.javaArgs` and `controller.resources` and are not top-level options. Signed-off-by: Robert Detjens <rdetjens@linuxfoundation.org>
The current OpenSearch Jenkins controller node is a c5.9xlarge (36c, 72GB). with a 100GB disk. This bumps the Jenkins controller pod resource requests to match that, less a bit to let it fit within a 9xlarge Kubernetes node after the K8S node system-reserved resource overhead. This also bumps the Java min/max heap size flags to use this higher memory, but this is a guess and should probably be tuned later. Signed-off-by: Robert Detjens <rdetjens@linuxfoundation.org>
vvalderrv
approved these changes
Dec 17, 2025
Signed-off-by: Robert Detjens <rdetjens@linuxfoundation.org>
vvalderrv
approved these changes
Dec 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 current OpenSearch Jenkins controller node is a
c5.9xlarge(36c, 72GB) with a 100GB disk (per current config inopensearch-project/opensearch-ci). This bumps the Jenkins controller pod resource requests to match that, less a bit to let it fit within a 9xlarge Kubernetes node after the K8S node system-reserved resource overhead.This also bumps the Java min/max heap size flags to use this higher memory, but this is a guess and should probably be tuned later.
EKS Auto Mode's autoscaler will automatically spin up the huge node for this and should not need any extra configuration.