Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Currently when a new EKS cluster is created, a default storageClass is deployed. The default settings for this storageClass includes setting allowVolumeExpansion: false.
Is there any reason why this is set to false by default? It seems to me that expansion of volumes would be something fairly common, and having to patch the StorageClass to allow expansion is an extra step which make the process less dynamic.
Would it not make more sense for the default setting to be allowVolumeExpansion: true ?
ckdarby
commented
3 years ago
Community Note
Tell us about your request Currently when a new EKS cluster is created, a default storageClass is deployed. The default settings for this storageClass includes setting
allowVolumeExpansion: false.Is there any reason why this is set to false by default? It seems to me that expansion of volumes would be something fairly common, and having to patch the StorageClass to allow expansion is an extra step which make the process less dynamic.
Would it not make more sense for the default setting to be
allowVolumeExpansion: true?