please enumerate mount options for the aws-ebs-csi-driver

[vstthomas]

/kind bug

This is a documentation bug. The release notes list Mount Options, that refer to the official Kubernetes docs. Their docs (indirectly) indicates that the aws-ebs-csi-driver does not support mount options.

Please post the mount options that are supported by the aws-ebs-csi-driver; below, for now. But somewhere longer-term, for future reference. I can't seem to find them anywhere.

Bonus: it would be super helpful if you posted some examples of very popular types as well. For example, in my case I'm creating a new storage class for on-cluster db operations with KubeDB.

[AndrewSirenko]

Hi @vstthomas, thank you for the feedback on needing clearer documentation for mount options. We will work on this.

In the meantime, you can find a list inside the StorageClass Parameters documentation page: aws-ebs-csi-driver/docs/parameters.md at master · kubernetes-sigs/aws-ebs-csi-driver

Here is a quick table of the supported options to unblock you at the moment:

Formatting Parameters	Description	xfs	ext3	ext4
"blockSize"	The block size to use when formatting the underlying filesystem.	✓	✓	✓
"inodeSize"	The inode size to use when formatting the underlying filesystem.	✓	✓	✓
"bytesPerInode"	The bytes-per-inode to use when formatting the underlying filesystem.		✓	✓
"numberOfInodes"	The number-of-inodes to use when formatting the underlying filesystem.		✓	✓
"ext4BigAlloc"	Formatting an ext4 filesystem using clustered allocation. See warnings in documentation page.			✓
"ext4ClusterSize"	The cluster size to use when formatting an ext4 filesystem using clustered allocation. See warnings in documentation page.			✓

[vstthomas]

excellent, thank you!

[vstthomas]

Regarding the bonus question: would AWS have configuration suggestions for FS options for databases on EKS?

[AndrewSirenko]

The EBS CSI Driver team does not have configuration suggestions for FS options for databases on EKS.

For more information on the use case for the ext4ClusterSize format option, see Torn write prevention - Amazon Elastic Compute Cloud.

[torredil]

/kind documentation

[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

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

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.