I have the following config map:

apiVersion: v1
data:
  config.yaml: |-
    inputRepo: "dummy_input"
    params:
      - _:
          CPU: "0.5"
          SIDECAR_CPU: "0.5"
          MAX_MEM: "700Mi"
          MEM: "500Mi"
          FORCE_PULL_IMAGE: "true"
      - stage3:
          AFTER: "stage2"
          PARALLELISM:  "2"
  stage1.tpl.yml: |-
    stage: dummy_stage1

    image: registry.gitlab.com/uit-sfb/metakube/pipeline-example/mk-sleep:0.2.0-SNAPSHOT

    entryScript: |
      $APP$ --fail $FAIL --duration $SLEEP --in $input --out $OUT/out

    input:
      pfs:
        name: input
        repo: dummy_input
        glob: "/metadata.sh"
  stage2.tpl.yml: |-
    stage: dummy_stage2

    image: registry.gitlab.com/uit-sfb/metakube/pipeline-example/mk-sleep:0.2.0-SNAPSHOT

    entryScript: |
      $APP$ --fail $FAIL --duration $SLEEP --in $input --out $OUT/out

    input:
       pfs:
         name: input
         repo: dummy_stage1
         glob: "/data/out"
  stage3.tpl.yml: |-
    stage: dummy_stage3

    image: registry.gitlab.com/uit-sfb/metakube/pipeline-example/mk-sleep:0.2.0-SNAPSHOT

    entryScript: |
      $APP$ --fail $FAIL --duration $SLEEP --in $input --out $OUT/out

    input:
       pfs:
         name: input
         repo: dummy_stage1
         glob: "/data/out"

which I mount to a container. I expect to get the 4 files defined in the CM, but what happens is that I do get the 4 files in addition to:

/home/sfb/pipeline/templates/..2020_02_25_18_48_05.754065631/stage1.tpl.yml
/home/sfb/pipeline/templates/..2020_02_25_18_48_05.754065631/config.yaml
/home/sfb/pipeline/templates/..2020_02_25_18_48_05.754065631/stage2.tpl.yml
/home/sfb/pipeline/templates/..2020_02_25_18_48_05.754065631/stage3.tpl.yml
/home/sfb/pipeline/templates/..data/stage1.tpl.yml
/home/sfb/pipeline/templates/..data/config.yaml
/home/sfb/pipeline/templates/..data/stage2.tpl.yml
/home/sfb/pipeline/templates/..data/stage3.tpl.yml

Those starting with '..' are actually symbolic links, but where to they come from?? I noticed that each time the pod restarts the path looking like a date changes. Any idea?

Here is the pod manifest:

apiVersion: v1
kind: Pod
metadata:
  ...
  name: metakube-mkadm-u0-ttzsn
  namespace: mktest3
spec:
  containers:
    - command:
        - bash
        - '-c'
        - /opt/docker/bin/mkadm -- pipeline apply --pachd $MK_PACHYDERM_ENDPOINT
      image: 'mkadm:0.2.0-SNAPSHOT'
      name: deploy
      resources:
        limits:
          cpu: '2'
          memory: 1Gi
        requests:
          cpu: 100m
          memory: 1Gi
      volumeMounts:
        - mountPath: /home/sfb/pipeline/configOverride
          name: conf-override
        - mountPath: /home/sfb/pipeline/templates
          name: templates
        - mountPath: /home/sfb/mnt/packages/..
          name: packages
  volumes:
    - configMap:
        defaultMode: 420
        name: metakube-pipeline
      name: conf-override
    - configMap:
        defaultMode: 420
        name: pipeline-templates
      name: templates
    - name: packages
      persistentVolumeClaim:
        claimName: metakube-packages
status:
...