Azure Dev Spaces was the choice for setup micro service based multi-branched developer environments on Azure. As it is retiring, Bridge to Kubernetes comes in as a replacement for Dev Spaces. It is said to be light weight as it runs as extensions to Visual Studio and VS Code.
In a world where solutions are distributed for multiple micro-services, it is important to have the agility to be part of teams where everyone rapidly contributes to solution changes. Gone are the days where we stay for a Pull Request to complete, sync code and run on our local environments. Bridge to Kubernetes provides to keep everything synced in and work on only the required portion of the code once branched.
As per the above image referenced via Microsoft Documentation, the solution has 3 components that are interconnected. These can be micro-services running on on a Kubernetes cluster or at production level can be part of any Paas offering.
Both Sussie and John are working on two different components while they might want to access the well tested and working. So rather than running multiple instances of different components, they can use a common platform and invite even more people in to collaborate.
In order to run Bridge to Kubernetes, you should not have enabled Azure Dev Spaces on that cluster. Also it currently only supports Linux containers.
Detailed instructions on What is Bridge to Kubernetes and how it can be setup is available here.
How to setup Bridge to Kubernetes on Visual Studio is explained in detail here.
Post a Comment