Local development deployments

Developers want fast iterations. When I make a code change to some code, I want to run the tests as soon as possible, and if something is wrong, to fix it as soon as possible. We've seen how well this works with unit tests. However, when the system uses a microservice architecture packaged as containers and deployed to a Kubernetes cluster, this is not enough. To truly evaluate the impact of a change, we often have to build an image (which may include updating Kubernetes manifests like Deployments, Secrets, and ConfigMaps) and deploy it to the cluster. Developing locally against Minikube is awesome, but even deploying to a local Minikube cluster takes time and effort. In Chapter 10, Testing Microservices, we used Telepresence to great effect for interactive debugging. However, Telepresence has its own quirks and downsides, and it's not always...