Add imagePullPolicy to API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
This is a possible optimization; since a Kip setup might use an image cache, we should be able to implement imagePullPolicy: if all the layers and metadata are present in the image cache for the container image, and imagePullPolicy is ifNotPresent or Never, then itzo will be able to start the container without (re)pulling the image.
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 locating the API definition and the code that decides whether a container image is pulled or started from the image cache. Trace how image layers and metadata are checked, then verify the requested ifNotPresent and Never behavior for cached and uncached images. Done means the API accepts imagePullPolicy and startup avoids pulling when the stated cache conditions are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100