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)

Storing sensitive data in OpenShift

In the modern world, applications are so complex that they are made up of multitudes of services interacting with each other via REST/SOAP APIs, binary protocols, message brokers, integration buses, and so on. An example of this is a backend application in an e-store; managing client orders means that you need to have access to the database with the products' details. Another example includes a payment processing application that must have access to international payment networks, such as SWIFT, in order to verify the card's details and process the payment. These examples are very different in terms of the scope and the technologies that are used, but they have a common trait—all services need some kind of authenticating piece of data to introduce themselves to each other and this data has to be stored somewhere.

An obvious...