Assigned
Status Update
No update yet.
Comments
go...@google.com
si...@workhouse.au
Is this feature being implemented any time soon?
In reference to GKE deployments, it's ridiculous to have 1TiB assigned for a persistent volume regardless of the size actually required.
If we need 5 2GiB volumes we end up with 5TiB of storage instead of 10GiB, quite the difference.
In reference to GKE deployments, it's ridiculous to have 1TiB assigned for a persistent volume regardless of the size actually required.
If we need 5 2GiB volumes we end up with 5TiB of storage instead of 10GiB, quite the difference.
ku...@gumtreegroup.com.au
Considering its P2 and S2, should we expect it to be implemented soon? Any timeline? This blocks us from using Filestore. Thanks.
ra...@gumtreegroup.com.au
And it starts at 2.5TB if someone wants SSD.
da...@venturesin.com
+1 - you can roll out windows VM's and disks on GC and it doesn't cost as much as the smallest filestore instance.
he...@google.com
Hello, any update on this?
em...@baselabs.mx
HI, this is also relevant for us. We are out of market for a software we want to build because we need small Filestore instances.
an...@gmail.com
+1 - for smaller architectures which require networked persistent storage, 1TiB is too much. It should be possible to start at 250GiB or at least be billed for used storage, not allocated capacity.
pe...@google.com
Hello Team can I please get an update on this is for Provisioning smaller size less than 1 TB for Filestore.
One of my customers is facing the same issue.
Description
What you would like to accomplish:
We would like to be able to create a Filestore instance with a size much smaller than 1 Tb as it is too expensive
How this might work:
We should be able to create Filestore instances from 1Gb
If applicable, reasons why alternative solutions are not sufficient: There are no alternatives at the moment