Live update for containers not built by Tilt
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
This is a feature request for having the live update feature work with containers not built by Tilt. Reasons:
- Moving images up and down the network can be a deal-breaking bottleneck for certain workflows, as reported by @jazzdan.
- There are security concerns to giving every developer push access to a container registry. I believe @drubin (Unu Motors) has mentioned this in the past.
- Not requiring users to have Docker installed locally would further our goal of making local development seamless.
A different solution to most of these concerns would be in-cluster building, but that's a separate discussion with its own trade-offs (e.g. you still wouldn't be able to use an off-the-shelf Ubuntu image and just live reload your code into it).
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
The issue does not identify files, tests, or entry points; begin by locating Tilt's existing live update implementation and the handling of images built by Tilt. Clarify the design for updating containers built elsewhere, then define tests and acceptance criteria for live updates without requiring local image builds or registry push access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100