Red Hat acquired Makara, a startup focused on deploying and managing applications across public and private clouds. The deal accelerated Red Hat’s plans for a Platform-as-a-Service (PaaS) offering, setting the foundation for what became OpenShift.
Red Hat launched OpenShift as a developer-facing PaaS. The early service emphasized self-service application deployment and scaling, helping establish OpenShift as a cloud platform rather than only a set of tools.
Red Hat released the OpenShift codebase as the OpenShift Origin project, intended to be the upstream community distribution behind the product. This made it possible to run OpenShift on your own infrastructure and contributed to wider adoption in on-prem and private cloud environments.
OpenShift 1.0 reached general availability, marking a milestone where early concepts matured into a stable, broadly usable platform. This helped organizations view OpenShift as production-ready, not just an experiment in cloud application deployment.
Red Hat released OpenShift Enterprise as an officially supported offering designed for enterprise customers. This marked a shift from primarily hosted developer use toward on-prem and private-cloud deployments with vendor support.
OpenShift Enterprise 2.0 shipped with updates that expanded supported “cartridges” (packaged runtimes and services) and improved the enterprise experience. This period focused on strengthening traditional PaaS features and integrations for data centers.
OpenShift Enterprise 2.2 emphasized integration with existing enterprise infrastructure and deployment automation. Red Hat highlighted automation through CloudForms and tighter operational controls, reflecting growing interest in hybrid cloud management.
In June 2015, Red Hat announced general availability of OpenShift Enterprise 3, a major shift toward containers. This release adopted Docker-formatted containers and used Kubernetes for orchestration, aligning OpenShift with emerging cloud-native standards.
Red Hat published OpenShift Container Platform (OCP) 3.0 documentation detailing “what’s new” and release notes for the 3.x generation. This helped standardize how enterprises planned upgrades and operationalized OpenShift clusters on their own infrastructure.
With the 3.10 release, Red Hat renamed the upstream project from “OpenShift Origin” to “OKD.” The change clarified the upstream/downstream relationship and reinforced OpenShift’s identity as a Kubernetes distribution, supporting broader hybrid cloud adoption through a clearer community pipeline.
OpenShift Container Platform 4 arrived in June 2019, and Red Hat described it as replacing OCP 3 as the current generation after about five years of OCP 3 being the primary release line. This transition mattered because it introduced a new operational model and architecture aimed at scaling hybrid cloud operations more consistently.
Red Hat extended support planning for OpenShift Container Platform 3.11 in 2020, acknowledging that many customers needed more time to migrate from 3.x to 4.x. This marked an important adoption reality: hybrid and on-prem platform upgrades often take longer than software release cycles.
Red Hat OpenShift: product releases and hybrid cloud adoption (2011–2020)