uselagoon / uselagoon/remote-controller
Deploy fails immediately on ImagePullBackoff
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
I had a deploy fail almost immediately when the kubectl-build-deploy-dind image went into ImagePullBackoff. Here's what happened:
- Started several deploys, got
successback from Lagoon API. - Lagoon build pods appeared.
- One build pod went into
ImagePullBackoff(the others started running). - The
ImagePullBackoffbuild pod disappeared. - Deploy shown as
failedin Lagoon dashboard:
I would have expected the pod to eventually start running instead of failing the deploy. The other builds started at the same time ran fine, so the image pull error may have just been a transient network issue?
I ran deploy on this environment a second time and it ran through fine.
Contributor guide
No contributing guide indexed for this repository
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 tracing the Kubernetes controller path that handles a build pod entering ImagePullBackoff and then disappearing. Reproduce or inspect the deploy failure flow described in the issue, and verify that a transient image-pull failure does not immediately mark the deploy as failed when the pod could still start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100