CSI Driver dont support minimum capacity as 128GB

[hariprasath91]

Hello Team ,

We see the CSI driver is provisioning with minimum capacity as 1 TIB for Enterprise Tier.
We use minimum capacity for enterprise as 128GiB which is allowed on GCP side .

Can we enable this feature in CSI driver as well , so that we can define 128GB size for PV creation ?

We want raise this as FR for enabling this on CSI driver .

Related Code:

gcp-filestore-csi-driver/pkg/csi_driver/controller.go

Lines 55 to 56 in 26c9bd3

	enterpriseTierMinSize = 1 * util.Tb
	enterpriseTierMaxSize = 10 * util.Tb

Regards,
Hariprasath.N

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[hariprasath91]

/remove-lifecycle stale

We are waiting for feedback from Google K8s Team .

Regards,
Hariprasath.N

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten