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)

Static IPs for external project traffic

The OpenShift scheduler takes all decisions regarding the placement of pods on nodes, taking into account factors such as the even distribution of pods, node affinity, and available resources. The whole point of default scheduling in OpenShift is to use of available resources as efficiently as possible, but it doesn't take into account the project pods that are created in them. The reason for this is that developers shouldn't be concerned with the placement of an applications' pods across the cluster, and that's why they have absolutely no control over where their pods end up. The problem starts to manifest itself in large organizations with multiple applications subject to different policies regarding security and compliance.

For example, an application handling bank account details must be subject to thorough audit...