CSI Certification Suite

Background

(P0) Basic sanity check BeforeEach test - make sure needed components are available
(P0) As a storage vendor I want to run a certification test against my CSI driver that validates it against the CSI SPEC.
(P0/P1) As a storage vendor & Kube admin I want to run a certification tests against my CSI driver that validates it against a CO
(P2) As a kube admin I want to validate that the CSI driver I’m using is the same one that was tested (ie. hash, version etc..)

The kubernetes-csi/csi-test test suite does the basic CSI API validation
- This is a sanity check that simply checks if the CSI driver conforms to the CSI Spec
- You can refer to this spreadsheet to see all the test cases that is covered by the sanity test

Clone the csi-test repo
Build the csi-sanity tool: cd go/src/github.com/kubernetes-csi/csi-test/cmd/csi-sanity/ and run make all
Run a CSI Driver (In this example the ebs csi driver is used)
- Launch an AWS EC2 instance, connect to it, and clone the driver repository
- cd go/src/github.com/bertinatto/ebs-csi/
- Install Dependencies: dep ensure
- Build: make ebs-csi-driver
- Run: bin/ebs-csi-driver -endpoint tcp://127.0.0.1:10000 -logtostderr -v 5
Run the sanity test on the ebs driver
- cd go/src/github.com/kubernetes-csi/csi-test/cmd/csi-sanity/
- ./csi-sanity -csi.endpoint 127.0.0.1:10000
The results of the test run will be printed