Kubernetes runner Helm Chart Values.yaml

Unable to get my head around the syntax to mount volumes to the Gitlab Runner.

Following the Documentation I was able to launch the runner using the helm chart.

The Syntax for attaching volumes is from here. [https://docs.gitlab.com/runner/executors/kubernetes.html#using-volumes] and it is in TOML language.

I cant get my head around to covert the below syntax and put it in the values.yaml file.
I am trying to mount some configmaps and secrets to the runner.

Can someone please help me with the sample snippet of the values.yaml ?

My values.yaml looks like below

imagePullPolicy: IfNotPresent
gitlabUrl: https://gitlab.com/
runnerRegistrationToken: “blahblahblahblahblahblahblahblahblahblahblahblahblahblahblah”
unregisterRunners: true
terminationGracePeriodSeconds: 3600
concurrent: 10
checkInterval: 30
logLevel: info
create: true
clusterWideAccess: true
enabled: true
image: mediaworks-docker-virtual.artifactory.adlm.nielsen.com/dockerimagefactory/ubuntu16-build-tools:16.4.0-16
imagePullSecrets: [“adlm-artifactory-secret”]
tags: “first-simple-runner”
privileged: true
namespace: gitlab-runners
pollTimeout: 180
outputLimit: 4096

  • name: empty-dir
    mount_path: /root/vikas
    medium: Memory
    cacheType: s3
    cachePath: “gitlab_runner”
    cacheShared: true
    s3ServerAddress: s3.amazonaws.com
    s3BucketName: useast1-nlsn-mdl-e-tam-mw-cloudteam-gitlab-cache-dev
    s3BucketLocation: us-east-1
    s3CacheInsecure: false
    secretName: s3access
    builds: {}
    services: {}
    helpers: {}
    fsGroup: 65533
    runAsUser: 100
    resources: {}
    affinity: {}
    nodeSelector: {}
    podAnnotations: {}
    podLabels: {}

I am also curious about this. When i look at the deployment.yml in the helm source code it does not have any handling for custom volumes. Is this an oversight? This might warrant an issue on gitlab