OpenShift Origin (OKD)

OpenShift Origin (OKD)
Name	OpenShift Origin (OKD)
Developer	Red Hat
Initial release	2011
Programming language	Go, Java, JavaScript
Operating system	Linux
License	Apache License 2.0

OpenShift Origin (OKD) OpenShift Origin (OKD) is an open source distribution of a container application platform originally developed by Red Hat and driven by contributors from multiple projects and organizations. It integrates container orchestration, developer tooling, networking, and CI/CD workflows to run cloud-native applications across on-premises and public cloud environments. OKD builds on projects such as Kubernetes, Docker, etcd, CoreOS, and CRI-O to provide a packaged platform for developers and operators.

Overview

OKD is positioned as the community upstream for the enterprise product and emphasizes interoperability with cloud infrastructure from Amazon Web Services, Google Cloud Platform, Microsoft Azure, and virtualization from VMware. The platform bundles components from the Cloud Native Computing Foundation ecosystem, including orchestration from Kubernetes, container runtime interfaces like containerd, and networking from projects such as Open vSwitch and CNI. OKD provides developer-focused features—source-to-image build automation influenced by GitHub workflows, integrated registry capabilities comparable to Docker Hub and Harbor, and pipeline automation similar to Jenkins and Tekton.

History and development

Development began as an upstream community project parallel to Red Hat’s commercial offerings and aligned with initiatives from Red Hat Enterprise Linux, Fedora, and CentOS engineering teams. The platform evolved through contributions from major vendors including IBM, Intel, Huawei, and SAP and adopted standards driven by the Open Container Initiative and the CNCF landscape. Key milestones track integration with Kubernetes after its rise in 2014, adoption of Operators modeled after best practices from CoreOS and Heptio, and migration of storage and networking integrations with projects like Ceph, GlusterFS, and OpenStack.

Architecture and components

The OKD architecture centers on a control plane of master components and a data plane of worker nodes, orchestrated by Kubernetes APIs and sustained by a distributed key-value store such as etcd. Core components include a web console inspired by designs from GNOME and KDE UX teams, a container registry patterned after Docker Registry, build controllers influenced by Source-to-Image concepts, and operators modeled after patterns popularized by CoreOS and Red Hat engineering. Networking leverages plugins compatible with the Container Network Interface and may incorporate Open vSwitch or OVN from Open vSwitch upstream. Storage integrates with Ceph, GlusterFS, NFS, and cloud provider block storage like Amazon EBS and Azure Disk. Authentication and identity management connect to LDAP, Active Directory, and identity providers using OAuth2 and OpenID Connect protocols.

Features and functionality

OKD exposes features used in modern application delivery: automated builds using concepts from GitLab and GitHub Actions, multi-tenant routing based on patterns from HAProxy and NGINX, continuous delivery pipelines comparable to Jenkins and Tekton, and extensibility through Kubernetes Operators inspired by Operator Framework. Developers use source repositories from Bitbucket and GitHub with CICD triggers, while operators manage scaling with autoscaling primitives akin to Horizontal Pod Autoscaler and advanced scheduling from kube-scheduler. The platform supports microservices architectures, service mesh integrations like Istio and Linkerd, and observability using Prometheus, Grafana, and Elastic Stack. Image management, vulnerability scanning, and policy enforcement align with practices from Open Policy Agent and Clair.

Deployment and installation

Installation options mirror cloud and on-prem strategies supported by providers like Amazon Web Services, Google Cloud Platform, Microsoft Azure, and virtualization via VMware vSphere. The project provides installer tooling influenced by Terraform and Ansible for automated provisioning, and exposes operators for lifecycle management drawn from patterns in Helm and Operator Lifecycle Manager. Installations can target bare-metal servers running Red Hat Enterprise Linux, CentOS Stream, or Fedora CoreOS, and leverage provisioning frameworks such as MAAS or Ironic for metal orchestration. High-availability setups use load balancers and distributed storage patterns found in HAProxy and Ceph deployments.

Community and governance

The OKD project is governed through an open community model with maintainers, contributors, and steering influences from Red Hat engineering and allied organizations like IBM and SUSE contributors. Development and roadmaps are coordinated via upstream repositories and public issue trackers hosted alongside work from Kubernetes SIGs, CNCF working groups, and related open source communities such as CoreOS and etcd maintainers. Contributions follow established open governance practices seen in Linux Foundation and Apache Software Foundation projects, with community meetings, RFC processes, and code review via GitHub and mailing lists.

Security and compliance

Security in OKD integrates container image scanning influenced by Clair and OpenSCAP, role-based access control mirroring Kubernetes RBAC and enterprise identity via LDAP and Active Directory. The platform supports network policies compatible with Calico and Cilium and enables encryption for etcd and API traffic using TLS practices endorsed by IETF standards. Compliance workflows often map to frameworks and audits referencing standards from NIST, ISO/IEC 27001, and requirements common in regulated sectors such as HIPAA and PCI DSS. Security updates and CVE management are coordinated with advisories from Red Hat and upstream project maintainers.

Category:Open source software