Chapter 4. Red Hat OpenShift components and architecture 61
4.1.4  Containerized services
Containerized services are infrastructure service functions, such as networking components 
and authorization. Most OpenShift internal services run as Docker containers that are 
managed by Kubernetes.
4.1.5  Run times and xPaaS 
Run times and xPaas are base container images that are ready for use by developers, each 
preconfigured with a particular runtime language or database. They can be used as-is or 
extended to add frameworks, libraries, and even other middleware products. The xPaaS 
offering is a set of base images for JBoss middleware products, such as JBoss EAP and 
ActiveMQ.
4.1.6  DevOps tools and user experience
OpenShift provides Web UI and CLI management tools for developers and system 
administrators, which enables the configuration and monitoring of applications and OpenShift 
services and resources. Web UI and CLI tools are built from the same REST APIs, which can 
be used by external tools, such as IDEs and CI platforms. OpenShift can also reach external 
SCM repositories and container image registries and bring their artifacts into the OpenShift 
cloud.
In addition to Docker and Kubernetes, OpenShift container platform adds source code 
management for developers, application management, user and group management, and 
networking infrastructure to give user access to the applications that are running in the 
cluster.
4.1.7  Master and nodes
An OpenShift cluster is a set of node servers that run containers and are centrally managed 
by a set of master servers. A master server can act as a node server, but for large OpenShift 
deployments, the recommendation is that those roles are segregated for increased stability. 
For more information about the recommended architecture for IBM Power Systems, see 
Chapter 5, “Red Hat OpenShift installation planning and considerations” on page 71.
Note: OpenShift does not hide the core Docker and Kubernetes infrastructure from 
developers and system administrators. Instead, it uses them for its internal services and 
allows importing raw containers and Kubernetes resources into the OpenShift cluster so 
that they can benefit from added capabilities. Also, Raw containers and resources can be 
exported from the OpenShift cluster and imported into other Docker-based infrastructures.