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)

Questions

  1. Which interface of OVS bridge is used to pass traffic from pods running on a particular node to and from pods running on other nodes?
    1. tun0
    2. br0
    3. veth...
    4. vxlan_sys_4789
  2. Suppose we have a multi-tenant environment with many applications developed by independent teams and outsource contractors that must be able to collaborate in rare cases, but for the most part must be totally isolated from each other. What is the simplest course of action to achieve that?
    1. Use the ovs-networkpolicy plugin and write custom network policies to enable omni-directional traffic between the projects used by those parties
    2. Use the ovs-subnet plugin
    3. Use the ovs-multitenant plugin and join and isolate projects as needed
    4. Use the plugin for a third-party solution, such as VMWare NSX-T or Tigera Calico
  1. What feature is best suited for whitelisting traffic coming from all pods in a specific project...