carvel-dev / carvel-dev/kbld

Remove need to use dockerhub for tests

Open
#193 1 comment 1 reaction 0 assignees View on GitHub
carvel accepted enhancement
Dominant language
Go
Stars
329
Forks
52
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem/challenge you have**
We are currently failing the tests due to rate limiting on Dockerhub

**Describe the solution you'd like**
We should stop relying on Dockerhub to have our e2e tests running in CI.

**Anything else you would like to add:**
Use a local registry like registry:2 or something similar. If we want to keep some tests that involve Dockerhub they should be scoped down to ensure that we do not get rate limited.

---
Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help work on this issue.

Contributor guide

Open the contributing guide

Research direction

The issue names no specific files or tests. Start by locating the e2e test setup and CI configuration, then trace where Dockerhub images are pulled; done means CI tests use a local registry without Dockerhub rate-limit failures, while any retained Dockerhub tests are scoped down.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
ci-cd, devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.