Deploy Deepfactor Portal With Resource Limits

This document describes the default resource limits and also how to edit them for Deepfactor portal pods during installation.

This document will only describe how to create the resource constraints to be passed to helm install/upgrade command. For a complete guide on portal installation please refer to the document Install Deepfactor portal using helm chart.

1. Create resource.yaml file as follows:

Please edit the resource limits as appropriate for your load and infrastructure.

postgres:
  containers:
    resources:
      requests:
        memory: 1Gi
        cpu: 1
      limits:
        memory: 8Gi
        cpu: 4

clickhouse:
  containers:
    resources:
      requests:
        memory: 1Gi
        cpu: 1
      limits:
        memory: 8Gi
        cpu: 4

symbolsvc:
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 500Mi
        cpu: 2

archivestore:
  containers:
    resources:
      requests:
        memory: 100Mi
        cpu: 50m
      limits:
        memory: 200Mi
        cpu: 100m

apisvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 100m
      limits:
        memory: 500Mi
        cpu: 200m

eventsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 150Mi
        cpu: 250m
      limits:
        memory: 250Mi
        cpu: 500m

statussvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 25m
      limits:
        memory: 50Mi
        cpu: 50m

proxysvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 100Mi
        cpu: 50m
      limits:
        memory: 200Mi
        cpu: 100m

alertstreamsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 1
      limits:
        memory: 1Gi
        cpu: 2

authsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 25m
      limits:
        memory: 100Mi
        cpu: 50m

persistentsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 500Mi
        cpu: 500m

notificationsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 25m
      limits:
        memory: 250Mi
        cpu: 250m

bomstreamingsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 1Gi
        cpu: 2
      limits:
        memory: 2Gi
        cpu: 4

dfwebscan:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 500m

nginx:
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 1

frontend:
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 1

updatersvc:
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 50m
      limits:
        memory: 100Mi
        cpu: 100m

dfstartup:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 25m
      limits:
        memory: 50Mi
        cpu: 50m

migrationsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 25m
      limits:
        memory: 50Mi
        cpu: 50m

policyctl:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 25m
        limits:
          memory: 50Mi
          cpu: 50m
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 25m
      limits:
        memory: 50Mi
        cpu: 50m

jobCleanup:
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 25m
      limits:
        memory: 50Mi
        cpu: 50m
2. Pass the above resource.yaml file in helm install/upgrade command
helm install df-stable deepfactor/deepfactor -n deepfactor \
  -f override.yaml \
-f resource.yaml \
  --set dfstartup.config.password=YOUR_PORTAL_PASSWORD \
  --set dfstartup.config.portalToken= \
   "YOUR_DEEPFACTOR_LICENSE_KEY_FROM_MY.DEEPFACTOR.IO"

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.