Signed-off-by: Derek Su <derek.su@suse.com>

Signed-off-by: Derek Su <derek.su@suse.com>

Retain will make the condition check in pod_test.go failed.

Signed-off-by: Derek Su <derek.su@suse.com>

Signed-off-by: justusbunsi <61625851+justusbunsi@users.noreply.github.com>

Signed-off-by: justusbunsi <61625851+justusbunsi@users.noreply.github.com>

drone env is somehow broken. Before moving CI to GitHub Actions, disable the e2e temporarily.

Signed-off-by: Derek Su <derek.su@suse.com>

add local-path-provisioner to ./deploy/chart in helm command

Signed-off-by: galal-hussein <hussein.galal.ahmed.11@gmail.com>

Signed-off-by: Derek Su <derek.su@suse.com>

Add the `pathPattern` parameter to the storage class values so it can
also be configured from the helm chart.

Signed-off-by: Alban Bedel <alban.bedel@aerq.com>

Add support for the `pathPattern` parameter, if set it is expanded as
a go template with the PV name and PVC metadata as input. This allow
configuring the provisioner to use predictable paths so volumes can be
prefilled externally or re-used.

Signed-off-by: Alban Bedel <alban.bedel@aerq.com>

Signed-off-by: Derek Su <derek.su@suse.com>

failed to start container "helper-pod": Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime creat │
│ e failed: runc create failed: unable to start container process: exec: "/manager": stat /manager: no such file or directory: unknown

I copied this example and had a really rough go as a kubernetes beginner; I needed a custom storageClass for the RabbitMQ operator.

So my pods were broken for a long while, until I changed my storageClass to match the other `local-path` storageClass already enabled in my cluster. This `rancher.io/local-path` seems to be the key to an easy deployment of custom storageClasses.

Signed-off-by: Derek Su <derek.su@suse.com>

This reverts commit bd0bc312.

Signed-off-by: Derek Su <derek.su@suse.com>

Signed-off-by: Derek Su <derek.su@suse.com>

Signed-off-by: Derek Su <derek.su@suse.com>

Signed-off-by: Derek Su <derek.su@suse.com>

feature: Add configuretion to run setup/teardown command in helper container instead of run with script

(cherry picked from commit a4c1f746)

This explicitly allows provisioning of NodePath-backed volumes with
access mode ReadWriteOncePod.

SharedFileSystemPath already implicitly supported the access mode.

Signed-off-by: Tobi Nehrlich <tobi@anothertobi.io>
(cherry picked from commit ce5a2a09)

`ReadWriteOncePod` was added with v0.22.x.

Signed-off-by: Tobi Nehrlich <tobi@anothertobi.io>
(cherry picked from commit 975e4773)

Signed-off-by: Tobi Nehrlich <tobi@anothertobi.io>
(cherry picked from commit bb9ad7ff)

(cherry picked from commit c558ea83)

(cherry picked from commit 8a3dd7a5)

(cherry picked from commit e5f0d0be)

Namely the values 'workerThreads', 'deletionRetryCount' and 'provisionRetryCount'.

There is some check in the main.go module which expects those to be a string so it can
convert them into an integer. Without this, we cannot actually provide the configuration
without hitting a conversion error. This should fix it.

(cherry picked from commit 7aa7e286)