Speed up testing by priming Kind cluster's docker registry with all required images
- Dominant language
- Go
- Stars
- 112
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Slow tests since all images need to be pulled from the remote docker registries for the first test case.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
Prime the Kind docker registry by prepopulating it with bookinfo, ambassador and workflow executor images.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
The issue concerns the Kind cluster's Docker registry used by tests; first locate the test-cluster setup and registry initialization entry point, then identify how the bookinfo, ambassador, and workflow executor images are obtained. Done means those images are available in the local registry before the first test case and test startup completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100