Adopt the Helm Chart from the deprecated repository

Switched to k8s 1.18.0 as attempt to fix issue #25

Setup automated builds using the release-tools

Signed-off-by: kmova <kiran.mova@mayadata.io>

Files are as is from deprecated repo

Use the steps at below link to setup automated builds via
release-tools.

https://github.com/kubernetes-csi/csi-release-tools

- add release-tools via git subtree
- update Makefile to use the release-tools/make
- add cloudbuild links from release-tools
- update Dockerfile that can be used for multi-arch by release tools
Signed-off-by: kmova <kiran.mova@mayadata.io>

git-subtree-dir: release-tools
git-subtree-mainline: 7d91f3d8
git-subtree-split: 3b6d17b1

Add GitHub multi-architecture pipeline

Enable mountOptions from StorageClass to PersistentVolume

Signed-off-by: Yonatan Kahana <yonatankahana.il@gmail.com>

cloud build: double the timeout, now 1 hour

Builds of external-snapshotter sometimes timed out because it builds
three images and that takes almost half an hour (the previous limit)
and more if the network is slow.

There's no good way to set timeouts per repo and a too high timeout
for shouldn't cause any issue, therefore the timeout gets increased
everywhere.

Add a flag to disable leader election

Related to #20.

allow export registry name

revert part of change

Fix the install of snapshot CRDs and controller

This PR installs snapshot CRDs and rbac rules from the repo
and installs snapshot controller from a local image if it is
a PR in external-snapshotter repo.
Otherwise it uses main or a stable version.

Cleanup

Update snapshot CRD version

Fix README.md formatting and remove duplicated parts

Signed-off-by: Radoslav Dimitrov <dimitrovr@vmware.com>

Update path creation and implemented possibility save data after removing PV

prow.sh: only run alpha tests for latest Kubernetes release

prow.sh: work around "kind build node-image" failure

Kind 0.9.0 accesses the "bazel-out" directory with a relative path,
which only works when the command is invoked inside the Kubernetes
source code
directory (https://github.com/kubernetes-sigs/kind/issues/1910).

Commit 7bcee13d added alpha feature gates for Kubernetes 1.19 in
the CSI_PROW_E2E_ALPHA_GATES_LATEST variable based on the comment in
https://github.com/kubernetes-csi/external-provisioner/pull/493#discussion_r502663402
that alpha testing only runs for the latest Kubernetes.

But some components (like external-health-monitor) are configured with
a single Prow job which runs the default set of tests on a stable
Kubernetes release (currently 1.17). Those tests used to include alpha
testing which then broke during Kind cluster startup because the
Kubernetes 1.19 feature gates weren't recognized by 1.17.

The solution is to disable alpha testing for Kubernetes != latest in
the default set of tests.

Add go ldflags using LDFLAGS at the time of compilation

prow.sh: update to kind 0.9, support Kubernetes 1.19