Add support for additional test infrastructure providers
- Dominant language
- Go
- Stars
- 83
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
e.g. Equinix, AWS, etc.
Adding this to the roadmap, but it will definitely need some longer-term design and discussion with the CNCF test infrastructure community to make sure that we're building on supported foundations. (`kubetest2`? `boskos`?).
There's no urgent need for this; this is a tracking issue in case we discover that we either want broader k8s coverage or better stability / performance / cost in the future. (i.e. @dprotaso is currently tracking down upgrade test failures on GKE 1.21 that aren't present on GKE 1.20, and it would be interesting to see if the same errors are present on other clouds / infrastructure.)
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the CNCF test infrastructure options mentioned—kubetest2 and boskos—and the existing GKE upgrade-test context; done would require a community-backed design for supported providers and a clear scope for broader coverage, stability, performance, or cost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, gcp, kubernetes
- Domain
- cloud, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100