actually it was just a lack of understanding on my part. Sorry for that! Hopefully !6544 (71e385e4) fixes it. Do you know how I could get the Pipeline to work?

FYI: I won't reply until monday :)

Hi @sroque-worcel

Thanks a lot for your reply! I don't see how my general approach is different from the linked one. !6512 adds support for more types of security contexts, my approach adds support for new types of volumes.

From looking at this MR, I see that I didn't update the docs. I would be happy to do so, when you tell me, that this MR is interesting for you!

BTW: I tried the [[runners.kubernetes.pod_spec]] yesterday and couldn't get it to work. With this config, there wasn't anything mounted in the pods:

        [[runners.kubernetes.pod_spec]]
            name = "nfs-mount"
            patch = '''
              containers:
              - name: build
                volumeMounts:
                - name: cache-nfs
                  mountPath: /cache
              - name: helper
                volumeMounts:
                - name: cache-nfs
                  mountPath: /cache
              volumes:
              - name: cache-nfs
                nfs:
                  server: foo.bar.baz
                  path: /path
                  readOnly: false
            '''

I also think it's a rather hacky way. Especially in the kubernetes context, embedding yaml in toml, that is embedded in yaml feels weird at least.

I got it to work by creating a NFS PVC like this https://docs.digitalocean.com/products/kubernetes/how-to/use-nfs-storage/ and mount it via:

        [[runners.kubernetes.volumes.pvc]]
          name = "gitlab-runner-cache-nfs"
          mount_path = "/cache"