An architect-level guide to bare-metal RHACM: hub and managed-cluster roles, SNO and compact three-node availability, installation lifecycle, and feature-scoped network flows. Includes four interactive animated diagrams and linked Red Hat references.

The architecture article drew storage as one layer in a larger platform. The networking article went deep on the network layer. This one does the same for storage. It follows a write from an application, through a volume mount, a claim, a storage class and a driver, down to the storage backend, and it ties the main claims to Red Hat's OpenShift Container Platform 4.22 documentation. Where the supplied whiteboard simplifies or blurs something, the text says so. The figures in

The architecture article drew networking as one layer in a larger platform. This one stays inside that layer. It follows a packet from a pod, across nodes, through a Service, in through the Ingress Controller, past network policy and out through an egress address, and it ties the main claims to Red Hat’s OpenShift Container Platform 4.22 documentation. Where a popular whiteboard diagram simplifies or blurs something, the text says so. The figures are redrawn, sharper original

In my first post, Learning Red Hat OpenShift, I covered why I picked OpenShift and what the platform promises. This post goes one level deeper: what is actually inside an OpenShift cluster, how the pieces talk to each other, and where the day-to-day tooling sits. I am using the architecture diagram below as the map for the article. Where a label on it has aged compared to Red Hat's current OpenShift Container Platform 4.x documentation (4.22 at the time of writing), I flag th

OpenShift is Red Hat's enterprise application platform for building, deploying and managing containerized applications, with Kubernetes at its core. Kubernetes on its own handles container orchestration; OpenShift adds what a production platform needs around it: a web console, integrated builds and CI/CD, monitoring and logging, security, and OperatorHub for installing and managing add-ons. It runs consistently across data centers, public clouds and the edge, either self-mana