Open romilbhardwaj opened 1 year ago
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.
This issue was closed because it has been stalled for 10 days with no activity.
We now have a temporary workaround for this.
Users can edit ~/.sky/config.yaml
to specify custom volumes and volume mounts to attach to their pods (docs):
pod_config:
spec:
containers:
- volumeMounts: # Custom volume mounts for the pod
- mountPath: /foo
name: example-volume
readOnly: true
volumes:
- name: example-volume
hostPath:
path: /tmp
type: Directory
Note that is not an ideal solution since config.yaml
would apply globally to all pods, and selecting volume mounts on a per-pod basis is not possible through this mechanism.
With #3689, we are able to set volume mount per task in the task yaml.
K8s users often have data locally stored on the cluster, typically in the form of a persistent volume + pvc, or a NFS mounted to all nodes, accessed via a hostpath.
From a user:
Our k8s features needs to add support for attaching and accessing data on persistent volumes, hostpaths and/or any other mechanism used by users to access their local data.