WIP: [do not merge] Resize ext4 filesystem on NodeStage

[jsafrane]

Is this a bug fix or adding new feature?
/kind feature

What is this PR about? / Why do we need it?
This PR illustrates changes needed on a CSI driver side to implement proposal in container-storage-interface/spec#452 (comment) (see the comment, not the PR!)

NodeStageVolume now checks, if resize of a filesystem is needed, and resizes it automatically if so. This makes NodeExpandVolume more or less redundant (for AWS EBS).

I've implemented only ext3/ext4 resize, xfs is to be done (xfs_info parser must be implemented). Alternatively, a CSI driver could always call resize2fs / xfs_growfs after mount, they should be idempotent and NOOP if a filesystem is already on its maximum size.

!!! Not to be merged !!! For exploration purposes only.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jsafrane]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coveralls]

Pull Request Test Coverage Report for Build 1273

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.8%) to 82.074%

---

Totals
Change from base Build 1269:	0.8%
Covered Lines:	728
Relevant Lines:	887

---

💛 - Coveralls

[k8s-ci-robot]

@jsafrane: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-aws-ebs-csi-driver-unit	936dae8	link	/test pull-aws-ebs-csi-driver-unit
pull-aws-ebs-csi-driver-verify	936dae8	link	/test pull-aws-ebs-csi-driver-verify
pull-aws-ebs-csi-driver-e2e-single-az	936dae8	link	/test pull-aws-ebs-csi-driver-e2e-single-az
pull-aws-ebs-csi-driver-e2e-multi-az	936dae8	link	/test pull-aws-ebs-csi-driver-e2e-multi-az

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[fejta-bot]

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.

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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/test-infra repository.

[k8s-ci-robot]

@jsafrane: PR needs rebase.

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/test-infra repository.