Add volume and volumeMount support to runner deployment
What does this MR do?
Add new entries in values to configure volumes
and volumeMounts
.
Why was this MR needed?
In order to support the macos Limited Availability, I have a CronJob downloading the customer allowlist to a volume, and that custom volume must be mounted in the runner
What's the best way to test this MR?
- Use the following values:
volumeMounts:
- name: allowlist
mountPath: /allowlist
volumes:
- name: allowlist
persistentVolumeClaim:
claimName: allowlist
- run
helm template release-name . -f values.yaml
- you get
volumeMounts:
- name: projected-secrets
mountPath: /secrets
//...
- mountPath: /allowlist
name: allowlist
volumes:
- name: runner-secrets
emptyDir:
medium: "Memory"
// ...
- name: allowlist
persistentVolumeClaim:
claimName: allowlist
What are the relevant issue numbers?
Edited by Adrien Kohlbecker