Book Image

Learn OpenShift

By : Denis Zuev, Artemii Kropachev, Aleksey Usov
Book Image

Learn OpenShift

By: Denis Zuev, Artemii Kropachev, Aleksey Usov

Overview of this book

Docker containers transform application delivery technologies to make them faster and more reproducible, and to reduce the amount of time wasted on configuration. Managing Docker containers in the multi-node or multi-datacenter environment is a big challenge, which is why container management platforms are required. OpenShift is a new generation of container management platforms built on top of both Docker and Kubernetes. It brings additional functionality to the table, something that is lacking in Kubernetes. This new functionality significantly helps software development teams to bring software development processes to a whole new level. In this book, we’ll start by explaining the container architecture, Docker, and CRI-O overviews. Then, we'll look at container orchestration and Kubernetes. We’ll cover OpenShift installation, and its basic and advanced components. Moving on, we’ll deep dive into concepts such as deploying application OpenShift. You’ll learn how to set up an end-to-end delivery pipeline while working with applications in OpenShift as a developer or DevOps. Finally, you’ll discover how to properly design OpenShift in production environments. This book gives you hands-on experience of designing, building, and operating OpenShift Origin 3.9, as well as building new applications or migrating existing applications to OpenShift.
Table of Contents (24 chapters)

DNS

One of the mechanisms for linking pods together, which has been discussed earlier in this book, relies on environment variables—the same as you would achieve by using plain Docker. When you deploy a multi-container application on OpenShift, pods that provide certain environment variables for pods that consume them must be started first, so that the variables are configured correctly by OpenShift. For example, if you deploy a 3-tier application consisting of a database, backend, and frontend, you will have to deploy the database first so that the backend pod picks up environment variables with the correct address and port for the database.

Pods can access each other's services directly via their IPs, but in a highly dynamic environment, where services may often be re-created, there is a need for a more stable solution. Aside from using environment variables, OpenShift...