Storage limit for builder pods in Kubernetes using Gitlab Runner Chart?

Hi, I was taking a look at this file and it looks like there is no way to limit the storage a builder pod can use.

Actually, I discovered this the hard way: A build pod in my Kubernetes cluster started downloading container images until there was no free space in the entire node where it was running, considerably slowing down the node and leaving it almost unusable.

The chart I use for gitlab Runner in Kubernetes is:

https://hub.helm.sh/charts/gitlab/gitlab-runner

I am running version 12.2.0

My current config for the chart is:

# Provides the runner orchestator for gitlab.com/fluidattacks

image: gitlab/gitlab-runner:alpine
imagePullPolicy: Always
gitlabUrl: https://gitlab.com/
runnerRegistrationToken: $FA_RUNNER_TOKEN
unregisterRunners: true
rbac:
  create: true
concurrent: 30
checkInterval: 10
metrics:
  enabled: false
runners:
  image: debian:stable-slim
  imagePullPolicy: always
  imagePullSecrets:
    - gitlab-reg
    - jfrog-reg
  privileged: false
  builds:
    cpuLimit: 900m
    memoryLimit: 5Gi
    cpuRequests: 500m
    memoryRequests: 1Gi
resources:
  limits:
    memory: 256Mi
    cpu: 200m
  requests:
    memory: 128Mi
    cpu: 100m
envVars:
  - name: RUNNER_EXECUTOR
    value: kubernetes

Is there any way to limit storage for build pods?