build e2e requirements for kind deployer

[elieser1101]

This should fix #184

This changes ensures e2e requirements can be found in _rundir/$KUBETEST2_RUN_DIR
as described in

kubetest2/pkg/testers/ginkgo/ginkgo.go

Line 50 in 696b358

UseBuiltBinaries bool `desc:"Look for binaries in _rundir/$KUBETEST2_RUN_DIR instead of extracting from tars downloaded from GCS."`

---

I replicatrd the same behavior from https://github.com/kubernetes-sigs/kind/blob/main/hack/ci/e2e-k8s.sh#L72-L86

[k8s-ci-robot]

Welcome @elieser1101!

It looks like this is your first PR to kubernetes-sigs/kubetest2 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubetest2 has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @elieser1101. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[aojea]

/ok-to-test

[aojea]

it looks correct but I couldn't test it neither will have time soon to do it

[elieser1101]

kubetest2 kind --build --test=ginkgo --up --down -- --focus-regex=<regex> --use-built-binaries

would be a new non blocking e2e test running the above passing be enough to help test this?

[aojea]

kubetest2 kind --build --test=ginkgo --up --down -- --focus-regex=<regex> --use-built-binaries

would be a new non blocking e2e test running the above passing be enough to help test this?

I'm fine with manual testing on this by now, have you verified it works?

/approve

defer final LGTM to @upodroid

[upodroid]

Thank you for the feature.

I'll open a new PR and adjust the CI to test kubetest2 kind deployer similar to the GCE one. https://github.com/kubernetes-sigs/kubetest2/blob/master/kubetest2-gce/ci-tests/updown-legacy.sh

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, elieser1101, upodroid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aojea,upodroid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment