Alex Kalenyuk created YUNIKORN-1253:
---------------------------------------
Summary: PVCs won't get past WaitForFirstConsumer with Apache
Yunikorn
Key: YUNIKORN-1253
URL: https://issues.apache.org/jira/browse/YUNIKORN-1253
Project: Apache YuniKorn
Issue Type: Bug
Components: shim - kubernetes
Reporter: Alex Kalenyuk
It seems that with Apache Yunikorn, WaitForFirstConsumer volume binding storage
classes are not supported (not sure if this is intended or not).
This makes it problematic to use storage that is not globally accessible from
all nodes:
[https://kubernetes.io/docs/concepts/storage/storage-classes/#volume-binding-mode]
To reproduce a simple failure to use a WaitForFirstConsumer binding-backed PVC:
```
kind: Pod
apiVersion: v1
metadata:
name: test
namespace: default
labels:
app: sleep
applicationId: "sleep0001-node-selector-test"
queue: "root.sandbox"
spec:
schedulerName: yunikorn
nodeSelector:
storage/ssd: 'true'
containers:
- name: test
resources:
limits:
cpu: 1
memory: 1G
requests:
cpu: 1
memory: 1G
image: busybox
command:
- sleep
- '1000000'
volumeMounts:
- name: scratch-volume
mountPath: /data
volumes:
- name: scratch-volume
ephemeral:
volumeClaimTemplate:
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: hostpath-provisioner
volumeMode: Filesystem
```
Storage used:
https://github.com/kubevirt/hostpath-provisioner-operator
A similar issue was spotted in:
[https://github.com/kubernetes/kubernetes/issues/86262]
And this PR seems to introduce the VolumeBinding filter but comments it out:
[https://github.com/apache/yunikorn-k8shim/pull/313]
I might be off with the "Bug" type here so feel free to correct me;
My thinking was that if introducing support for WFFC is trivial, this may make
sense to exist in older versions too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
