We finally get to the last post of the series, and in this post I will introduce you to the tool that Developers will be using soon. It’s still not final and yet many features need to be planned and included, but will overcome all the problems I described in my previous posts. There’s already a good blog post from Lalatendu Mohanty about what CDKv3 is so I will not go into many details.

At the time OpenShift started, we realized that having a local development environment was important to make iterative development work more agile. Back then, the requirements that we had for a local development environment were pretty clear: It needs to work on linux, mac and windows It needs to be easy to run It needs to be easily disposable Resources used need to be adjustable

OpenShift v3 launched a year and a half ago and during this time we’ve been looking at different ways to run a local OpenShift development environment on the developer’s laptop. In this series of articles I will be introducing the options we have been providing and most importantly, I will describe the evolution in our approach.. But before digging into any particular solution, we need to set the ground rules of what a local development environment is and why it is important.