Resource requirements

By default, the charts set no resource requests or limits. For any environment carrying real traffic, set requests and limits explicitly.

The published baseline

Per-component minimums are maintained in System requirements:

Component	CPU	Memory	Storage
`postgres`	8	16Gi	1Ti SSD/NVMe
`redis`	2	32Gi	20Gi
`rabbitmq`	4	8Gi	100Gi
`file-storage`	8	8Gi	1Ti SSD/NVMe
`control-center`	4	4Gi	100Gi
`identity-service`	4	4Gi	50Gi
`api-gateway`	4	8Gi	50Gi
`callback-service`	4	4Gi	50Gi
`download-service`	4	4Gi	50Gi
`ometascan`	See the MetaDefender Core requirements

Requests and limits use the standard Kubernetes resources block. Every component in both charts accepts it. Update override-values.yaml in Quick start

# --- Instance ---

workers:

ometascan:

resources:

requests: { cpu: "4", memory: 4Gi, ephemeral-storage: 200Gi }

limits: { cpu: "8", memory: 16Gi, ephemeral-storage: 200Gi }

# The API Gateway and Callback Service have the same allowance.

api-gateway:

resources:

requests: { cpu: "4", memory: 4Gi, ephemeral-storage: 50Gi }

limits: { cpu: "4", memory: 4Gi, ephemeral-storage: 50Gi }

callback-service:

resources:

requests: { cpu: "4", memory: 8Gi, ephemeral-storage: 50Gi }

limits: { cpu: "4", memory: 8Gi, ephemeral-storage: 50Gi }

download-service:

resources:

requests: { cpu: "4", memory: 4Gi, ephemeral-storage: 50Gi }

limits: { cpu: "4", memory: 4Gi, ephemeral-storage: 50Gi }

helm upgrade mdcluster ./mdcluster --install -f ./override-values.yaml

Last updated on

Was this page helpful?