[
https://issues.apache.org/jira/browse/SPARK-55496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Darmanovic updated SPARK-55496:
-------------------------------------
Description:
Most cloud providers today provide kubernetes storageClasses with
allowVolumeExpansion set to true. This, paired with a PVC monitoring and
scaling service like the [Kubernetes Volume
Autoscaler|[https://github.com/DevOps-Nirvana/Kubernetes-Volume-Autoscaler]]
allows the user to provision PVCs that can expand with growing storage
requirements, saving costs by not over-provisioning. This expansion is done by
simply increasing the storage request in the PVC's definition.
This approach however, presents a problem in the current code base, as there is
a check in the replacePVCsIfNeeded function that matches the desired size with
the existing pod definition, which would suddenly be ineligible for re-use
after being expanded.
I propose a simple 1-character change that would allow disks with the same *or
greater* size to be re-used. I will shortly make a PR with this change.
was:
Most cloud providers today provide kubernetes storageClasses with
allowVolumeExpansion set to true. This, paired with a PVC monitoring and
scaling service like the [Kubernetes Volume
Autoscaler|[https://github.com/DevOps-Nirvana/Kubernetes-Volume-Autoscaler],]
allows the user to provision PVCs that can expand with growing storage
requirements, saving costs by not over-provisioning. This expansion is done by
simply increasing the storage request in the PVC's definition.
This approach however, presents a problem in the current code base, as there is
a check in the replacePVCsIfNeeded function that matches the desired size with
the existing pod definition, which would suddenly be ineligible for re-use
after being expanded.
I propose a simple 1-character change that would allow disks with the same *or
greater* size to be re-used. I will shortly make a PR with this change.
> Support reuse of scaled PVCs
> ----------------------------
>
> Key: SPARK-55496
> URL: https://issues.apache.org/jira/browse/SPARK-55496
> Project: Spark
> Issue Type: Improvement
> Components: Kubernetes
> Affects Versions: 3.5.8, 4.1.1
> Reporter: Filip Darmanovic
> Priority: Trivial
> Labels: features
>
> Most cloud providers today provide kubernetes storageClasses with
> allowVolumeExpansion set to true. This, paired with a PVC monitoring and
> scaling service like the [Kubernetes Volume
> Autoscaler|[https://github.com/DevOps-Nirvana/Kubernetes-Volume-Autoscaler]]
> allows the user to provision PVCs that can expand with growing storage
> requirements, saving costs by not over-provisioning. This expansion is done
> by simply increasing the storage request in the PVC's definition.
> This approach however, presents a problem in the current code base, as there
> is a check in the replacePVCsIfNeeded function that matches the desired size
> with the existing pod definition, which would suddenly be ineligible for
> re-use after being expanded.
> I propose a simple 1-character change that would allow disks with the same
> *or greater* size to be re-used. I will shortly make a PR with this change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
