Drive e2e-Framework Tests using Dagger

[vladimirvivien]

What do you want to see?

I came across Dagger and thought it would be a great tool to integrate with e2e-Framework tests. Dagger provides programmatic constructs to describe and implement build/publishing for CI/CD pipelines. Think of Dagger as a fancy/modern Makefile (instead you write your steps in languages like Go, Python, and Typescript).

There are minor overlaps between Dagger and e2e-Framework step functions. Both e2e-Framework steps functions and Dagger functions can be used to handle environment setup and teardowns. However, Dagger goes much further as it is designed for handling these steps. Dagger can

• Setup containerized environment
• Run unit tests (would trigger e2e-framework tests)
• Build code into containers
• Publish containers to repository

Proposal

• Write an example documentation that shows how to use Dagger to drive e2e-framework test
• Possibly create a default Dagger module, under third_party/dagger/modules that:
  • Setup test environment
  • Initialize Kind cluster
  • Launch test e2e-framework tests
  • Clean up
• Investigate better integration with Dagger

Extra Labels

No response

[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

[vladimirvivien]

/remove-lifecycle stale

[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

[vladimirvivien]

/remove-lifecycle stale

[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