From bc0b66545771a2cddbc62037d866d1e2b5dfa9c6 Mon Sep 17 00:00:00 2001 From: Ilyes Ben Dlala Date: Fri, 1 Sep 2023 16:53:14 +0200 Subject: [PATCH] #1305 Add note about resource limits Add a note to inform users about the resource limits for the persistence-defectdojo hook. Signed-off-by: Ilyes Ben Dlala --- .../persistence-defectdojo/.helm-docs.gotmpl | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/hooks/persistence-defectdojo/.helm-docs.gotmpl b/hooks/persistence-defectdojo/.helm-docs.gotmpl index 0f1f79f0ec..162854414f 100644 --- a/hooks/persistence-defectdojo/.helm-docs.gotmpl +++ b/hooks/persistence-defectdojo/.helm-docs.gotmpl @@ -46,6 +46,28 @@ For scan types which are not supported by DefectDojo, the generic importer is us sophisticated display of the results and fewer features inside DefectDojo. In the worst case, it can lead to some findings being lost - see the note below. +:::note +A big amount of findings may require higher resource limits. Changing them may be required to avoid OOM errors. +The default values are: +```yaml +requests: { + cpu: "200m", + memory: "100Mi" +}, +limits: { + cpu: "400m", + memory: "200Mi" +} +``` + +For example, to set the memory limit to 512Mi, we run the following command: + +```bash +helm upgrade --namespace NAMESPACE --install persistence-defectdojo secureCodeBox/persistence-defectdojo --set="hook.resources.limits.memory=512Mi" +``` +::: + + :::caution Be careful when using the DefectDojo Hook in combination with other ReadAndWrite hooks. By default, the secureCodeBox