Reproducible Development and Deployment with Bazel and Telepresence
summary
Bazel produces hermetic reproducible builds and can emit distroless images that do not depend on a distro; the demo builds an app, loads Bazel image into Docker, and proves identical output across builds. Telepresence provides a two‑way proxy that exposes internal IPs, volumes and environment variables and in Telepresence container mode runs a pod that routes cluster traffic to the local process. Workflow swaps a cluster deployment to the laptop (works) but replaces that deployment for other developers.
AI-written summary · about
chapters (14)
- 0:00Start
- 8:17include an external dependency
- 13:07launching a container
- 16:19development environment
- 17:28building and executing inside docker
- 18:56build our docker image
- 19:19containerize your building environment and basil
- 20:20run a local containerized application in the cloud
- 23:12creating a reproducible deployment
- 24:44loading this image into the local registry
- 25:30load this image inside the local registry
- 28:37use multiple namespaces in your development environment
- 29:46setting up the proxy
- 31:15swap the deployment
related talks
36mSeamless Development Environments on Kubernetes using Telepresence - Ara Pulido
15mReproducible research using Bazel
36mUsing Bazel for Fast, Correct Docker Deployments
42mUse Your Favorite Developer Tools in Kubernetes With Telepresence
11mIntroducing Remote Bazel
42mIntegrating with ease: Leveraging BuildStream interaction with Bazel build
30mIntro: Telepresence
26mBuilding Go with Bazel