Use Helm chart manifests in the e2e tests

[mauriciopoppe]

So our e2e tests create a test cluster and install LVP using go code

sig-storage-local-static-provisioner/test/e2e/e2e_test.go

Line 296 in 8335a2a

setupLocalVolumeProvisioner(ctx, config, nil)

sig-storage-local-static-provisioner/test/e2e/e2e_test.go

Line 311 in 8335a2a

createProvisionerDaemonset(ctx, config)

And if you look at the implementation it's installing the same resources declared in the helm chart, to avoid duplicating the setup we could set up a helm go client and install the chart in helm/provisioner/ with some values defined in go code instead.

I think https://manuelmazzuola.dev/2021/03/28/deploy-helm-chart-go is good starting point to use helm programatically, another way to accomplish the same is to install the helm/kubectl binaries in the script that creates the cluster that way we can call helm debug | kubectl apply -f - from within the test

The starting point for the test runner is our Prow job in test-infra which calls make e2e -> hack/e2e.sh ->

sig-storage-local-static-provisioner/hack/e2e.sh

Lines 318 to 324 in e0ad13e

	go run $ROOT/hack/e2e.go -- "${kubetest_args[@]}" \
	--deployment "$DEPLOYMENT" \
	--up \
	--down \
	--test-cmd bash \
	--test-cmd-args="$ROOT/hack/run-e2e.sh" \
	"$@"

if you have a cluster already running make sure to update the above lines to only run the test and not create/delete a cluster, i.e. remove --up --down

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[mauriciopoppe]

/remove-lifecycle rotten
/lifecycle frozen

[jennwah]

/assign

Hi @mauriciopoppe , I can help on this issue. But i need some help as I not sure how to go about this

[mauriciopoppe]

I updated the description with more info, hope it helps

[jennwah]

Sure, the description looks good to me. Will give this a try when I have some time on hand later on. Will ping you once I am done with the PR