Add e2e test framework

[benmoss]

Builds off of #3566.

Adds adapted tests from the e2e suite. Right now there only a subset but ideally over time we can backfill additional coverage as we figure out how to do it in vendor agnostic ways.

cc @elmiko

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: benmoss
To complete the pull request process, please assign aleksandra-malinowska after the PR has been reviewed.
You can assign the PR to them by writing /assign @aleksandra-malinowska in a comment when ready.

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

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS

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

[elmiko]

thanks @benmoss , this is gonna take some time for me to go through. just a heads up ;)

[benmoss]

The main changes are in test/framework, the rest is just noise. We might want to consider dropping the vendor/ directory as part of #3566 since it generates a bunch of commit noise

[elmiko]

We might want to consider dropping the vendor/ directory as part of #3566 since it generates a bunch of commit noise

that makes sense to me.

i want to spend some time thinking about how we integrate this into the wider testing infra. i like that this is self-contained and we could just build by importing, i guess the next steps will be to figure out if we should promote subdirectories in the cloudproviders to contain their implementations.

[k8s-ci-robot]

@benmoss: PR needs rebase.

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/test-infra repository.

[elmiko]

hey Ben, just wanted to give a heads up. i am still working my way through this pr. currently trying to get everything working with the cluster-api-autoscaler-provider. it's going slow but i think most of it is making sense.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[elmiko]

/remove-lifecycle stale

[mwielgus]

There seems to be no progress on the PR. Closing. Feel free to reopen once needed.

[elmiko]

@mwielgus i would like to continue with this work, but at this point i think it's best to just open a new pr when i am ready to move forward.