breaking(CSI-314): remove legacy volume support

[sergeyberezansky]

TL;DR

Removed support for legacy volumes (without binding to REST API client). This change is breaking.

What changed?

• Removed XATTR implementation of volume capacity tracking
• Removed support for volumes not having API client bound
• Removed "dev mode" support to run CSI sanity without actual mount of Weka filesystem (incomplete)
• Removed tests that were run on emulated weka filesystem locally. Instead, only NFS-based CSI sanity is performed.

How to test?

1. Deploy CSI driver with and without NFS enabled
2. Perform NFS functional regression testing

Why make this change?

The previous implementation had performed NFS client group registration attempt on each mount, causing lots of additional API calls and reducing overall performance of volume provisioning and publishing. This change breaks the process into 2 parts, while client registration is performed during API client initialization, while only the NFS permission is ensured during mount.

[sergeyberezansky]

• chore(deps): optimize CSI sanity speed during CI #438
• refactor(CSI-318): add configurable wait for filesystem / snapshot deletion #437
• refactor(CSI-272): move NFS client registration to APIClient startup rather than on each mount #436
• breaking(CSI-314): remove legacy volume support #435 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[graphite-app]

Graphite Automations

"Request reviewers once CI passes" took an action on this PR • (01/28/25)

1 reviewer was added to this PR based on Sergey Berezansky's automation.