Implement a kubetest2 tester for e2e-framework

[vladimirvivien]

This is a marker issue to indicate that this project should have a Kubetest2 tester implemented. Kubetest2 can stand up an environment and/or lunch tests. It has several providers implemented including kind, gce, etc.

Adding a kubetest2 tester would allow this project to delegate environment startup/tear down to kubetest2 and reuse existing providers. I propose that the implementation be contributed to the kubetest2 project to make it easy to build/run.

Test writers who are looking to adopt kubetest2 can use this project to write tests and use the kubetest2 binary to launch the test similar to the following:

kubetest2 kind -v 2 \
  --up \
  --down \
  --test=e2e-framework \
  --assess='boombap'
  --skip-assessment='network'

[tyxeron]

This would be super nice. We are currently looking for an end-to-end test framework to test our k8s setup. How far down the road would you guess this feature is? Is there currently a workaround for this?

[vladimirvivien]

Hi @tyxeron there is currently no one immediately working on this. It's mostly a nice to have since the e2e framework provides its own programmatic way of managing test lifecycles including the ability to launch external environments.

Please take a look at the examples for ways of running end-to-end tests using code that can launch kind as part of the test lifecycle. While kind is the only env that is inherently supported, the api is easy to support any env.

Hope that helps

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[vladimirvivien]

/remove-lifecycle stale

[vladimirvivien]

See kubernetes-sigs/kubetest2#218

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[vladimirvivien]

/remove-lifecycle stale