Use official CSI Release Tools

[maennchen]

Use official CSI release-tools for testing / building.

[ofek]

I'm on Windows, so I'd need it to support it. Does it? I quite like the current invoke tooling btw

[maennchen]

@ofek I would really like it at least for the E2E tests. It seems very hard to run them otherwise.

We could keep building via invoke but use it to run the tests. What do you think?

Does the driver itself work on Windows btw?

[ofek]

Sure! It only works as containerized plugin, not locally (since Windows doesn't have fuse). Docker for Win/Mac provides a Linux VM that everything actually runs in

[maennchen]

@ofek How far should the Windows support go then? Only for Building the Image or also testing?

I'm asking because the official test suite including E2E contains a lot of Bash to setup a K8S Cluster correctly etc.

I like the invoke setup as well, I would prefer to stay as close to the spec & official tooling though.

[ofek]

Can we run stuff in containers? Building Docker plugins doesn't work on Windows so I run dind https://hub.docker.com/_/docker

See https://github.com/ofek/docker-volume-gcs/blob/master/build.py

[maennchen]

@ofek I think we could easily do it this way:

• Provide release tools for *NIX users (Makefile)
• Provide a cmd/ bat / whatever we need for windows that starts all of that inside docker (dind) and calls the Makefile in there

[ofek]

Sounds good, though why not just do that all the time? Seems cleaner and more reproducible for everyone imo

[maennchen]

Why not we can just expose that entrypoint script for Everyone. :)

[maennchen]

Setting up prow is too much work for not enough benefit for this project.

We'll instead improve the CI (#27) and setup E2E Tests (#28).