| filename | sha512 hash |
|---|---|
| v0.4.0.zip | 2f46b54211178ad1e55926284b9f6218be874038a1a62ef364809a5d2c37b7bbbe58a2cc4991b9cf44cbfe4966c61dd6c16df0790627dffac4f7df9ffc084a0c |
| v0.4.0.tar.gz | 0199df52ac1e19ee6b04efb80439024dde11de3d8fc292ce10527f2e658b393d8bfd4e37a6ec321cb415c9bdbee83ff5dbdf58e2336d03fe5d1b2717ccb11169 |
- Update Kubernetes cluster to 1.14+ before installing the driver, since the released driver manifest assumes 1.14+ cluster.
- storageclass parameter's
fstypekey is deprecated in favor ofcsi.storage.k8s.io/fstypekey. Please update the key in you stroage parameters.
See details for all the changes.
- Make secret optional (#247, @leakingtapan)
- Add support for XFS filesystem (#253, @leakingtapan)
- Upgrade CSI spec to 1.1.0 (#263, @leakingtapan)
- Refactor controller unit test with proper mock (#269, @zacharya)
- Refactor device path allocator (#274, @leakingtapan)
- Implementing ListSnapshots (#286, @zacharya)
- Add max number of volumes that can be attached to an instance (#289, @bertinatto)
- Add helm chart (#303, @leakingtapan)
- Add volume expansion (#271, @bertinatto)
- Remove cluster-driver-registrar (#322, @jsafrane)
- Upgrade to golang 1.12 (#329, @leakingtapan)
- Fix bugs by passing fstype correctly (#335, @leakingtapan)
- Output junit to ARTIFACTS for testgrid (#340, @wongma7)
| filename | sha512 hash |
|---|---|
| v0.3.0.zip | 27a7a1cd4fc7a8afa1c0dd8fb3ce4cb1d9fc7439ebdbeba7ac0bfb0df723acb654a92f88270bc68ab4dd6c8943febf779efa8cbebdf3ea2ada145ff7ce426870 |
| v0.3.0.tar.gz | 9126a3493f958aaa4727bc62b1a5c545ac8795f08844a605541aac3d38dea8769cee12c7db94f44179a91af7e8702174bba2533b4e30eb3f32f9b8338101a5db |
- None
Driver upgrade should be performed one version at a time by using following steps:
- Delete the old driver controller service and node service along with other resources including cluster roles, cluster role bindings and service accounts.
- Deploy the new driver controller service and node service along with other resources including cluster roles, cluster role bindings and service accounts.
See details for all the changes.
- Strip symbol for production build (#201, @leakingtapan)
- Remove vendor directory (#198, @leakingtapan)
- Use same mount to place in the csi.sock, remove obsolete volumes (#212, @frittentheke)
- Add snapshot support (#131, @tsmetana)
- Add snapshot examples (#210, @tsmetana)
- Implement raw block volume support (#215, @leakingtapan)
- Add unit tests for ControllerPublish and ControllerUnpublish requests (#219, @sreis)
- New block volume e2e tests (#226, @dkoshkin)
- Implement device path discovery for NVMe support (#231, @leakingtapan)
- Cleanup README and examples (@232, @dkoshkin)
- New volume snapshot e2e tests (#235, @dkoshkin)
| filename | sha512 hash |
|---|---|
| v0.2.0.zip | a9733881c43dfb788f6c657320b6b4acdd8ee9726649c850282f8a7f15f816a6aa5db187a5d415781a76918a30ac227c03a81b662027c5b192ab57a050bf28ee |
| v0.2.0.tar.gz | 0d7a3efd0c1b0c6bf01b08c3cbd48d867aeab1cf1f7f12274f42d561f64526c0345f23d5947ddada7a333046f101679eea620c9ab8985f9d4d1c8c3f28de49ce |
- Upgrade the Kubernetes cluster to 1.13+ before deploying the driver. Since CSI 1.0 is only supported starting from Kubernetes 1.13.
Driver upgrade should be performed one version at a time by using following steps:
- Delete the old driver controller service and node service along with other resources including cluster roles, cluster role bindings and service accounts.
- Deploy the new driver controller service and node service along with other resources including cluster roles, cluster role bindings and service accounts.
See details for all the changes.
- Update to CSI 1.0 (#122, @bertinatto)
- Add mountOptions support (#130, @bertinatto)
- Resolve memory addresses in log messages (#132, @bertinatto)
- Add version flag (#136, @dkoshkin)
- Wait for volume to become available (#126, @bertinatto)
- Add first few e2e test cases #151 (#151, @dkoshkin)
- Make test-integration uses aws-k8s-tester (#153, @kschumy)
- Rename VolumeNameTagKey (#161, @leakingtapan)
- CSI image version and deployment manifests updates (#171, @dkoshkin)
- Update driver manifest files (#181, @leakingtapan)
- More e2e tests (#173, @dkoshkin)
- Update run-e2e-test script to setup cluster (#186, @leakingtapan)
- Check if target path is mounted before unmounting (#183, @sreis)
| filename | sha512 hash |
|---|---|
| v0.1.0.zip | 03841418496e292c3f91cee7942b545395bce049e9c4d2305532545fb82ad2e5189866afec2ed937924e144142b0b915a9467bac42e9f2b881181aba6aa80a68 |
| v0.1.0.tar.gz | 106b6c2011acd42b0f10117b7f104ab188dde798711e98119137cf3d8265e381df09595b8e861c0c9fdcf8772f4a711e338e822602e98bfd68f54f9e1c7f8f16 |
- Update driver name and topology key (#105, @leakingtapan)
- Add support for creating encrypted volume and unit test (#80, @leakingtapan)
- Implement support for storage class parameter - volume type (#73, @leakingtapan)
- Implement support for storage class parameter - fsType (#67, @leakingtapan)
- Add missing capability and clusterrole permission to enable tology awareness scheduling (#61, @leakingtapan)
- Wait for correct attachment state (#58, @bertinatto)
- Implement topology awareness support for dynamic provisioning (#42, @leakingtapan)
- Wait for volume status in e2e test (#34, @bertinatto)
- Update cloud provider interface to take in context (#45, @leakingtapan)
- Initial driver implementation (9ba4c5d, @bertinatto)