Build image and push to registry for production deploy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
As requested by a user in #tilt: https://kubernetes.slack.com/archives/CESBL84MV/p1586782788168800
is it possible to get tilt to just build images and push them to a registry, w/o deploying the k8s manifests? Kind of like make ? (edited)
To clarify, you want a build+push images mode for deploying to prod? And something else would deploy the k8s configs?
Tilt is currently focused on the development workflow. But inherent in that is very much how to make the developer experience production-focused (and thus, user-focused) in the first place. We should have a better experience / integrations / recommended best practices to build images and have them in a registry to be eventually deployed.
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
No files, tests, or entry points are named in the issue. First clarify the intended build-and-push workflow and how it should avoid deploying Kubernetes manifests; done would be a defined production-oriented mode with agreed behavior and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100