Hands-On Microservices with Kubernetes

Cluster per developer

Creating a cluster per developer is the ultimate level of isolation. The developer doesn't have to worry about breaking other people's code or being impacted by other people's code. However, there are some significant downsides for this approach, such as the following:

• It is often too expensive to provision a full-fledged cluster for each developer.
• The provisioned cluster often doesn't have high fidelity with the production system.
• You will generally still need another integration environment to reconcile changes from multiple teams/developers.

With Kubernetes, it may be possible to utilize Minikube as a local cluster per developer and avoid many of the downsides.