> Markdown version of [/videos/851-developing-locally-with-kubernetes-a-guide-and-best-practices](https://www.wearedevelopers.com/videos/851-developing-locally-with-kubernetes-a-guide-and-best-practices). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Developing locally with Kubernetes - a Guide and Best Practices Are hardware limits and cloud bills bottlenecking your microservices? Discover how hybrid debugging routes remote Kubernetes traffic directly to your local IDE, saving you time and money. - **Speakers:** Dan Erez - **Event:** WeAreDevelopers LIVE - **Published:** February 6, 2024 - **Duration:** 39:20 - **URL:** https://www.wearedevelopers.com/videos/851-developing-locally-with-kubernetes-a-guide-and-best-practices ## Summary Transitioning from simple monolithic applications to complex microservices introduces significant integration and testing hurdles. As development environments expand, engineering teams inevitably hit local hardware constraints. Moving these workflows entirely to a remote cloud environment introduces hefty cloud infrastructure costs and "traffic collisions" when multiple developers test against the same shared services. Organizations are forced to find a sustainable middle ground that balances operational costs with developer agility. To solve this, there are several Kubernetes strategies ranging from strictly local setups to hybrid models. Local Kubernetes distributions like `kind` (Kubernetes in Docker), Minikube, K3s, and MicroK8s allow developers to replicate production topologies cleanly without racking up cloud bills. For mitigating high AWS or private cloud expenses, teams might even explore experimental distributed computing concepts—repurposing the idle CPU power of thousands of employee laptops as a decentralized, "free" internal cloud to handle container workloads. The most practical insight for modern engineering teams is optimizing the inner developer loop using a hybrid debugging methodology. By utilizing tools like Telepresence along with a shared, central Kubernetes cluster, organizations can route targeted remote traffic directly to an individual developer's local IDE via HTTP headers. This eliminates the need to constantly wrap, build, and deploy containers for every code tweak while simultaneously preventing service disruptions for other developers working in the same staging environment. **Keywords:** microservices development patterns, local kubernetes distributed computing, kubernetes in docker (kind), minikube alternatives, telepresence traffic interception, shared testing clusters, cloud infrastructure optimization, integration testing workflows, developer traffic collisions, local code debugging, testcontainers framework, shift-left devops, rapid iteration developer loops, k3s edge environments, hybrid debugging methodologies ## Chapters 1. **Advantages and complexities of microservice architectures** (00:00) — Breaking monoliths into independently scalable modules introduces massive routing and configuration overhead. 1. **Testing microservice integrations with containerized dependencies** (06:41) — Complex business logic requiring numerous distinct microservices quickly outgrows simple local unit testing flows. 1. **Comparing local, remote, and hybrid Kubernetes testing models** (11:43) — Traffic collisions and escalating public cloud costs necessitate strategic test environment design. 1. **Utilizing idle employee devices for distributed cluster computing** (16:30) — Harnessing unused laptop memory across an enterprise hardware fleet drastically reduces private cloud expenses. 1. **Benefits and constraints of local Kubernetes development environments** (20:00) — Replicating production topologies locally avoids network dependencies but introduces steep learning curves for teams. 1. **Evaluating lightweight Kubernetes distributions for local development** (24:02) — Choosing between multi-node containers and simple binary distributions depends on specific developer resource availability. 1. **Debugging remote cluster workloads locally with network interception** (28:31) — Routing targeted testing flow traffic back to a local machine avoids rebuilding application images continually. 1. **Demonstrating cluster deployment and live traffic interception** (33:20) — Capturing remote service function calls directly handles live runtime calculations inside a local developer environment. 1. **Selecting the appropriate container development testing methodology** (37:52) — Engineering teams should progressively adopt container orchestrators only when multi-dependency environments dictate. ## Related Moments - [Understanding Kubernetes core components and local environment tools](https://www.wearedevelopers.com/videos/242-microservices-how-to-get-started-with-spring-boot-and-kubernetes) (from "Microservices: how to get started with Spring Boot and Kubernetes") - [Addressing local development challenges with Podman Desktop](https://www.wearedevelopers.com/videos/1133-containers-and-kubernetes-made-easy-deep-dive-into-podman-desktop-and-new-ai-capabilities) (from "Containers and Kubernetes made easy: Deep dive into Podman Desktop and new AI capabilities") - [Deploying local container pods to Kubernetes clusters](https://www.wearedevelopers.com/videos/1133-containers-and-kubernetes-made-easy-deep-dive-into-podman-desktop-and-new-ai-capabilities) (from "Containers and Kubernetes made easy: Deep dive into Podman Desktop and new AI capabilities") - [Decomposing infrastructure problems using sandbox environments and networking tools](https://www.wearedevelopers.com/videos/1055-how-i-saved-200k-yr-in-direct-costs-writing-0-code-lines-in-k8s) (from "How I saved 200K/yr in direct costs writing 0 code lines in K8s") - [Optimizing software development for production and Kubernetes](https://www.wearedevelopers.com/videos/383-kubernetes-native-java) (from "Kubernetes Native Java") - [Transitioning from monolith architectures to microservices and Kubernetes](https://www.wearedevelopers.com/videos/108-get-ready-for-operations-by-pull-requests) (from "Get ready for operations by pull requests") ## Related Articles - [Learning Kubernetes made easy with KubeCampus](https://www.wearedevelopers.com/magazine/348-learning-kubernetes-made-easy-with-kubecampus) - [Mastering Remote Work: Tips for Developers](https://www.wearedevelopers.com/magazine/558-mastering-remote-work-tips-for-developers) - [Remote, Hybrid, or In-Office: What’s Really Best for Developers?](https://www.wearedevelopers.com/magazine/638-remote-hybrid-or-in-office-what-s-really-best-for-developers) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) ## Related Jobs - [Platform Engineer (DevOps)](https://www.wearedevelopers.com/jobs/48264-platform-engineer-devops) at **WDW Consulting GmbH** - [Lead Cloud DevSecOps Engineer - Kubernetes](https://www.wearedevelopers.com/jobs/ext/1659167-lead-cloud-devsecops-engineer-kubernetes) at **BWI GmbH** - [Devops Engineer](https://www.wearedevelopers.com/jobs/ext/1940926-devops-engineer) at **Bitpanda** - [Software Engineer, Platform Engineering (L2)](https://www.wearedevelopers.com/jobs/ext/1956829-software-engineer-platform-engineering-l2) at **Twilio** - [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub** - [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**