OpenShift provides different options for building and deploying containers on the platform. These generally include: Build and deploy from application source code - Users can specify the location of their source code in a GIT repository. OpenShift will build the application binaries, then build the container images that include those binaries and deploy to OpenShift. Users can also specify a dockerfile as the source code to build container images from.
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.
In this blog, I’m going to describe what are my requirements when looking for a way to develop locally using OpenShift, and I’ll describe a tool I have created to help me with this workflow. First of all, I have to say that I’m not only a developer, so maybe the workflow I’m looking for is too complex, so I’m still experimenting to refine not only the workflow but also the tooling.