Explore cache refresh interval for prepull-daemonset
Open
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
One option for this might be to use a sleep for a configurable interval in the pause container. Since the daemonset defaults to restartPolicy: Always then it should just restart and pull the images again
Originally posted by @dbkegley in https://github.com/rstudio/helm/pull/154#discussion_r810252061
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
Start by locating the prepull-daemonset and its pause container configuration, then inspect how restartPolicy: Always affects image pulling. Determine how a configurable sleep interval would control refreshes; done means the daemonset has a defined, configurable cache refresh behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100