Articles in this section

Deploy Deepfactor Portal With Resource Limits Follow

Avatar
DeepFactor Support
  • Updated

This document describes how to specify resource limits for Deepfactor portal micro-services during installation.

This document will only describe how to create the resource yaml file 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.

dfstartup:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
   containers:
     resources:
      requests:
        memory: 250Mi
        cpu: 100m
      limits:
        memory: 250Mi
        cpu: 200m
webappsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 500m
  zapPod:
    memLimit: 16Gi
    memReq: 8Gi
apisvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 100m
      limits:
        memory: 1Gi
        cpu: 1
alertsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 100m
      limits:
        memory: 4Gi
        cpu: 2
authsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 25m
      limits:
        memory: 100Mi
        cpu: 50m
cvesvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 500m
      limits:
         memory: 1Gi
         cpu: 2
depchecksvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 500m
      limits:
        memory: 4Gi
        cpu: 1
eventsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 2Gi
        cpu: 2
notificationsvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 25m
      limits:
        memory: 100Mi
        cpu: 50m
proxysvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 100Mi
        cpu: 50m
      limits:
        memory: 200Mi
        cpu: 100m
symbolsvc:
  containers:
    resources:
      requests:
        memory: 100Mi
        cpu: 50m
      limits:
        memory: 250Mi
        cpu: 200m
statussvc:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 25Mi
        cpu: 10m
      limits:
        memory: 500Mi
        cpu: 200m
nginx:
  containers:
    resources:
      requests:
        memory: 250Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 1
dfwebscan:
  initContainers:
    wait:
      resources:
        requests:
          memory: 25Mi
          cpu: 10m
        limits:
          memory: 250Mi
          cpu: 200m
  containers:
    resources:
      requests:
        memory: 500Mi
        cpu: 250m
      limits:
        memory: 1Gi
        cpu: 500m
archivestore:
  containers:
    resources:
      requests:
        memory: 100Mi
        cpu: 50m
      limits:
        memory: 200Mi
        cpu: 100m
clickhouse:
  containers:
    resources:
      requests:
        memory: 1Gi
        cpu: 1
      limits:
        memory: 8Gi
        cpu: 4
postgres:
  containers:
    resources:
      requests:
        memory: 1Gi
        cpu: 1
      limits:
        memory: 4Gi
        cpu: 2
updatersvc:
  containers:
    resources:
      requests:
        memory: 50Mi
        cpu: 50m
      limits:
        memory: 100Mi
        cpu: 100m
 

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"

 

Related articles

Comments

0 comments

Please sign in to leave a comment.