refact e2e test config enhancing setup, logging, steps and documenting hooks

[mtulio]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR introduce several updates in the e2e loadbalancer reachable e2e test cases targeting to:

• enhance the e2e documentation on hooks utilization
• encapsulating test case configuration/data into a single container
• enhance ginkgo steps and framework logging

The main motivation of this PR is to increase the flexibility to add new test cases with customization without losing existing reachable test configuration. This is an isolated PR from broad/unrelated changes from #1214

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

This issue is currently awaiting triage.

If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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.

[k8s-ci-robot]

Hi @mtulio. Thanks for your PR.

I'm waiting for a kubernetes 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.

Details

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.

[mtulio]

results of e2e tests locally:

$./e2e.test --ginkgo.v  --ginkgo.focus 'loadbalancer'
  W0718 10:49:13.164350  313350 test_context.go:478] Unable to find in-cluster config, using default host : https://127.0.0.1:6443
  Jul 18 10:49:13.164: INFO: The --provider flag is not set. Continuing as if --provider=skeleton had been used.
Running Suite: AWS Cloud Provider End-to-End Tests 
=========================================================================================
Random Seed: 1752846553 - will randomize all specs

Will run 5 of 8 specs
SS
------------------------------
[...]
------------------------------

Ran 4 of 8 Specs in 1194.446 seconds
SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 4 Skipped
PASS

[mtulio]

Hi, this PR is ready for review. PTAL?

[elmiko]

/ok-to-test

[elmiko]

this mostly makes sense to me, i just had a question about one of the refactoring choices you made. fwiw, it's not a blocker for me, i'm just curious.

[mtulio]

looks like flag, re-testing:
/test pull-cloud-provider-aws-e2e-kubetest2

[mtulio]

/assign @kmala @elmiko

[mtulio]

This PR is ready for final review. Thanks @elmiko for feedback.

[elmiko]

this makes sense to me, thanks for adjusting the config function.

/lgtm

[kmala]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kmala

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [kmala]

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