Open Thermi opened 7 years ago
@kubernetes/sig-apps-feature-requests
Though this doesn't place the specification directly in the volumeClaimTemplate
, perhaps https://github.com/kubernetes/kubernetes/pull/45345 will get you what you need once it's available?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen
comment.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta
.
/lifecycle stale
/remove-lifecycle stale /lifecycle frozen
@Thermi does #45345 fix your issue? If now, what else is missing?
Well, I guess it could. It'd be better though to have it as a part of a claim, because then it can be specified in the application's kubernetes file, instead of having to create a seperate StorageClass each time a new FS is required.
This would be a productive feature. Is it still in the pipeline to be added?
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No,
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): volumeClaimTemplates fstype
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature Request
Currently, (at least following the API documentation), there is no way to specify an fsType in a volumeClaimTemplates. Some applications (mongodb) that fit the use case of a statefulSet should use a specific file system for some reason (performance). It is therefore desired to make this specifyable.