ROX-33431: Bump memory resources for rpms-signature-scan#3206
Conversation
Scanner-db* containers suffer the same OOMs as central-db and scanner-v4-db did and which got patched in stackrox/stackrox#20655 Replicating the same to the Scanner repo. Saw OOMs in these pods in the last 7 days: - scanner-db-slim-on-push-598gl-rpms-signature-scan-pod - scanner-db-slim-on-push-m9v7z-rpms-signature-scan-pod
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/retest scanner-db-slim-on-push |
|
/retest scanner-on-push |
|
/retest scanner-db-on-push |
|
/retest scanner-slim-on-push |
|
/retest scanner-db-on-push |
|
/retest scanner-db-slim-on-push |
|
/retest scanner-on-push |
|
/retest scanner-slim-on-push |
|
/konflux-retest scannr-db-on-push |
msugakov
added
the
disable-konflux-auto-retest
|
/retest |
|
/retest |
|
@msugakov: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1 participant
Scanner-db* containers suffer the same OOMs as central-db and scanner-v4-db did and which got patched in
stackrox/stackrox#20655
Replicating the same to the Scanner repo.
Saw OOMs in these pods in the last 7 days:
I'm not going to backport this PR to any
release-*branches because I think the gain is small. Scanner V2 isn't actively changed.