Cross-cloud integration testing
Open
Nobody has claimed this yet.
area/build
area/debug
area/test
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
What problem are you trying to solve?
The subtle differences between cloud providers are starting to create a host of issues. See #2174, #2173, #1648 for examples. These are hard to replicate, debug and understand what might impact users after a release.
How should the problem be solved?
- Tooling to create clusters on the cloud providers with common configuration.
- Default RBAC, PSP and k8s components (such as helm).
- Installation of specific Linkerd versions.
- Target testing clusters, run the integration tests.
- Allow for long running tests (longer than 24 hours).
- Run tests in parallel on each provider.
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 reading the related issues #2174, #2173, and #1648, then review the repository's existing integration-test entry points. Done means tooling can create similarly configured clusters across cloud providers, install specified Linkerd versions, run integration tests in parallel, and support tests lasting longer than 24 hours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, devops, infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100