Ephemeral volume scheduling problems

[kangzhiqin]

What would you like to be added?

I have two ephemeral volumes, one that requires 100M of memory and one that requires 43G of memory.

After the 100 MB volume is successfully scheduled, only 42 GB memory is available on the node. As a result, the second volume fails to be created, and the pod fails to be scheduled.

However, other nodes in the cluster have sufficient space.

Why is this needed?

Is there a good way to solve this problem?

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[neolit123]

/sig storage

[xing-yang]

@kangzhiqin as a workaround, can you combine the two volumes and use subpath for different mounts?
Does localcsi driver support storage capacity tracking? If it relies on that feature, enhancement is still needed as it currently only supports one PVC per Pod.

[xing-yang]

/triage needs-more-information

[k8s-ci-robot]

@xing-yang: The label(s) triage/needs-more-information cannot be applied, because the repository doesn't have them.

In response to this:

/triage needs-more-information

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[xing-yang]

/triage needs-information

[kangzhiqin]

@kangzhiqin as a workaround, can you combine the two volumes and use subpath for different mounts? Does localcsi driver support storage capacity tracking? If it relies on that feature, enhancement is still needed as it currently only supports one PVC per Pod.

Thank you for your reply. I'll think about this solution.

[kangzhiqin]

@kangzhiqin as a workaround, can you combine the two volumes and use subpath for different mounts? Does localcsi driver support storage capacity tracking? If it relies on that feature, enhancement is still needed as it currently only supports one PVC per Pod.