Read more about OpenShift Basics

Download all the Free PDF files (2023 Guides)

OpenShift v4, developed by Red Hat, represents a significant evolution in the way containerized applications are deployed and managed. Here’s a simplified overview of its architecture, topology, and key components:

Architecture

1. Kubernetes-based Foundation: OpenShift v4 is built upon Kubernetes, an industry-standard for container orchestration, ensuring high scalability and manageability of containerized applications.
3. Operator Framework: This version introduces the Operator framework, which simplifies the deployment and management of complex Kubernetes applications. Operators act like automated site reliability engineers for their respective applications.
5. Immutable Infrastructure: It employs an immutable infrastructure model where the environment is consistent and unchanged throughout the application lifecycle, enhancing security and stability.
7. Enhanced Security: Security is a cornerstone, with features like automated system updates and built-in authentication and authorization.

Topology

1. Master Nodes: These nodes control and manage the OpenShift cluster. They host essential components like the API server, etcd (for cluster state storage), controller manager, and scheduler.
3. Worker Nodes: These nodes run the application containers. They are managed by the master nodes and house pods, which are the smallest deployable units in Kubernetes.
5. Infrastructure Nodes: Optional, but often used for running internal OpenShift services like routers, registry, and logging/metrics collectors.

Key Components

1. etcd: A reliable distributed data store that persistently stores the cluster’s configuration and state.
3. API Server: Serves the Kubernetes API, the front end of the Kubernetes control plane.
5. Scheduler: Responsible for assigning work, in the form of pods, to worker nodes.
7. Controller Manager: Manages a set of core Kubernetes controllers.
9. Container Runtime: Enables container execution; OpenShift v4 supports CRI-O as a lightweight container runtime.
11. Red Hat CoreOS (RHCOS): The default operating system for OpenShift nodes, tailored for container workloads and secure by default.
13. Networking: Implements a CNI (Container Network Interface) compatible model for network connectivity between pods and external services.
15. Routing and Service Mesh: Manages external access to services and enhances microservices communication.
17. Registry: Integrated container image registry for managing images within the OpenShift environment.
19. Monitoring and Logging: Integrated tools for monitoring the health of the cluster and applications, and for collecting and analyzing logs.

This architecture makes OpenShift v4 a robust, scalable, and secure platform for managing containerized applications across various environments.

Different OpenShift Topology:

OpenShift v4 topologies and their explanations:

1. Single Node OpenShift (SNO): This topology is ideal for edge computing, small environments, or development purposes. It runs all services on a single node, making it resource-efficient but limited in terms of high availability and scalability.
3. Standard Multi-Node Cluster: This is the most common topology, consisting of multiple master and worker nodes. It offers high availability, scalability, and load balancing. Master nodes handle the control plane, while worker nodes run the applications.
5. Multi-Zone Cluster: In this topology, nodes are distributed across different availability zones or data centers. This setup enhances high availability and disaster recovery by ensuring that the cluster remains operational even if one zone fails.

Compact Cluster: A compact cluster has both master and worker roles on the same set of nodes. This setup is resource-efficient while still providing some level of high availability and scalability, suitable for medium-sized deployments.