Migrate e2e tests on `kind`
Open
Nobody has claimed this yet.
area/roadmap
area/test-infra
kind/feature
lifecycle/frozen
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
tektoncd/pipeline and probably other migrated to use kind for e2e tests.
- It's easier to run the same environment locally and on the cluster
- It's less flaky and it's quicker to provision
- It's less costly (and can allow us to run multiple e2e tests on different k8s version, …)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's e2e tests and the existing Kubernetes test provisioning, then compare them with the kind-based approach used by tektoncd/pipeline. Done means the e2e tests are migrated to kind while preserving their existing test coverage and supporting the same environment locally and on the cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100