Pod Resource Requirements

Kubernetes allows you to specify the required amount and limits of CPU and memory used by a Pod.

note

For details of how resources requirements work, please refer to the Kubernetes documentation on requests and limits.

Default Resources

The chart is defined without resources as recommended in Helm and Kubernetes. This allows the cluster to adjust and scale as required.

We recommend that you use the QuickCase chart with this configuration and only set resources when operational behaviour requires them.

Example or Reference Resources

caution

Use the default of no resource constraints before exploring these options.

The Java apps, data-store and definition-store have traditionally been the first to require any resource constraints.

The following are example resource configurations that have been used and have worked in the past. Our recommendation is that you use them as a starting point and that you use them on a case by case basis per app. I.e. don't just enable all of them at once.

case_ui:
  resources:
    requests:
      memory: 64Mi
      cpu: 25m
    limits:
      memory: 512Mi
      cpu: 500m

admin_ui:
  resources:
    requests:
      memory: 64Mi
      cpu: 25m
    limits:
      memory: 512Mi
      cpu: 500m

data_store:
  resources:
    requests:
      cpu: 500m
      memory: 512Mi
    limits:
      cpu: 1000m
      memory: 1024Mi

definition_store:
  resources:
    requests:
      cpu: 500m
      memory: 512Mi
    limits:
      cpu: 1000m
      memory: 1024Mi

attachment_store:
  resources:
    requests:
      memory: 64Mi
      cpu: 25m
    limits:
      memory: 512Mi
      cpu: 500m