This relies on a slightly different deployment script: a "deploy.sh"
must exist which knows that it has to dump a test driver configurion
into the file pointed to with CSI_PROW_TEST_DRIVER, if that env
variable is set.

That way, we no longer need to know what capabilities the installed
driver has.

fix incorrect link

Document the process for releasing a new sidecar

Update hostpath driver version to get fix for connection-timeout

Update snapshotter to version v2.0.0

Signed-off-by: Grant Griffiths <grant@portworx.com>

Fix overriding of junit results

Update prow hostpath driver version to 1.3.0-rc2

Fix version_gt to work with Kubernetes prefix

Signed-off-by: Grant Griffiths <grant@portworx.com>

Enable snapshot tests in 1.17 to be run in non-alpha jobs.

This requires adding one more parallel e2e test run with
a special focus flag because snapshot tests are still guarded
with a "[Feature:VolumeSnapshotDataSource]" tag. The setting that
skips all tests with "[Feature:.*]" has to be removed because it
overrides the focus.

We don't have serial snapshot tests yet. This needs to be modified
again if we add any in the future.

Improve README by adding an explicit Kubernetes dependency section

fix syntax for ppc64le build

Improve snapshot-controller running check and version_gt to support multiple formats 

Enable topology testing with hostpath driver

Signed-off-by: Grant Griffiths <grant@portworx.com>

Create a kind cluster with two worker nodes so that the topology feature can be tested. Test cases that test accessing volumes from multiple nodes need to be skipped

Use kind v0.6.0

kind v0.6.0 appends the kubeconfig with the default config at
~/.kube/config.

Adding build for ppc64le

Add snapshotter CRDs after cluster setup

Signed-off-by: Grant Griffiths <grant@portworx.com>

delete kind cluster after tests run

Inside a real Prow job it is better to clean up at runtime instead of leaving that to the Prow job cleanup code because the later sometimes times out.
Signed-off-by: Mucahit Kurt <mucahitkurt@gmail.com>

prow.sh: also log output of system containers

Depending on the error, those logs are needed to debug failures.

prow.sh: use vendor directory if available

This avoids dependencies on the Go module cache or the upstream code
hosting.

Go version 1.13, helper scripts

Some operations are sensitive to the version of Go that is used. In
the past, formatting of source differed depending on the
version. Right now it is the content of the vendor directory which
changes when switch back and forth between 1.12 and 1.13.

We don't want to impose a certain workflow on developers, like forcing
all invocations of Go to run inside a container. If developers want
that, they can set up their development environment accordingly.

But we should warn about this aspect to raise awareness. "make"
invocations which involve Go now compare against the projects Go
version (specified in travis.yml) once at the beginning. This is only
a warning because we don't know which future version will be
compatible with the project.

Vendor directory handling gets updated, too: verification is now a
separate script (became too complex for make) and there is a
corresponding "update-vendor.sh". In contrast to verification,
updating vendor is not integrated into make and thus itself invokes
the go version check.