make run/controlplane fails: minio/minio was removed from Docker Hub
Open
Beginner friendly
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened
make run/controlplane fails on a fresh setup because the MinIO image cannot be pulled: minio/minio:RELEASE.2020-08-26T00-00-49Z
The MinIO pod stays in ImagePullBackOff, which causes controlplane-server and controlplane-ops to stay at Init:0/1.
Extends #6380
How to reproduce
make up/local-cluster
make run/controlplane
kubectl get pods -n pipecd
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
Search the repository for the MinIO image reference minio/minio:RELEASE.2020-08-26T00-00-49Z used by the make run/controlplane entry point. Run make up/local-cluster, then make run/controlplane and inspect the pods with kubectl get pods -n pipecd; done means the MinIO image pulls successfully and the controlplane pods can leave their waiting states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 76/100