Chapter 5. Automating Builds
Chapter 3 looked at how applications can be deployed to an OpenShift cluster by running commands to create Kubernetes objects and pulling container images from a central container registry. However, most applications are developed and updated over time after their first deployment.
This is especially true for software that is not running on a local device (such as a word processor) but on a cloud platform, like an OpenShift cluster. Shipping software to consumer devices is a much more involved process than updating cloud software, which is one reason many products move to produce cloud software.
Software that is running as a web service is usually accessed from a consumer device with a web browser or client. The software itself can be upgraded by the developing company at any time. Many companies even deploy updates multiple times a day.
For a company that is running all workloads in containers on OpenShift, such as the example game developer described in this book, the process of creating and updating container images needs to be automated and reproducible. Nobody wants to just sit there and create and deploy container images all day long.
This chapter is all about creating an automated procedure to bring code that developers wrote on their machines to the OpenShift cluster where it’s meant to run.
Luckily, OpenShift already brings several tools to help with this process.
OpenShift Image Builds
The first of the tools this chapter looks ...
Get Operating OpenShift now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
