OpenShift
In plain English
Plain definition
OpenShift is a container application platform built on Kubernetes. It packages the container orchestration engine together with build tools, developer workflows, security controls and an administrative console so that teams can run containerised applications without assembling every underlying component themselves.
What OpenShift adds to Kubernetes
Red Hat’s OpenShift extends the upstream Kubernetes API with additional resources and controllers, including Routes for ingress, ImageStreams and BuildConfigs for source-to-image builds, Security Context Constraints (SCCs) for pod-level security enforcement, and an integrated OperatorHub for lifecycle-managed add-ons. OpenShift ships in several variants, including self-managed OpenShift Container Platform and managed cloud offerings. It is usually installed with its own installer and upgraded through its Operator-based update mechanism, rather than by managing raw Kubernetes components directly.
Why teams run OpenShift
Operations and platform teams usually come to OpenShift when they need a supported, opinionated Kubernetes platform with built-in multi-tenancy controls, integrated CI/CD primitives and a consistent update path across clusters. Its stricter security defaults, particularly SCCs that restrict container privilege, are one of the most common sources of trouble when deploying workloads whose manifests were written for vanilla Kubernetes.
How it sits on Kubernetes
OpenShift runs directly on top of Kubernetes. Every native Kubernetes object (Pods, Deployments, Services) remains valid, while OpenShift adds its own API groups and cluster Operators to manage networking (via Routes and the router), image handling, authentication integration, and cluster configuration. The platform itself is run largely through Kubernetes Operators, so cluster lifecycle management is expressed as declarative custom resources rather than imperative scripts.
Exposing a service with a Route
A team exposing an internal web service outside the cluster would typically create an OpenShift Route resource pointing at an existing Service, instead of relying only on a Kubernetes Ingress object. The Route uses the integrated router and TLS termination behaviour that OpenShift provides by default.
Why it is not just renamed Kubernetes
OpenShift is not simply “Kubernetes with a different name.” Its default security constraints (such as SCCs denying root-level container execution unless explicitly permitted) and its Operator-driven lifecycle model mean that manifests, permissions and upgrade procedures written for generic Kubernetes often need changes before they will run on OpenShift.
Terms to know alongside OpenShift
- Kubernetes
- Operator
- Security Context Constraint (SCC)
- Route
- OperatorHub
Further Reading
Red Hat’s official OpenShift product documentation is the authoritative description of OpenShift, its supported variants and version-specific capabilities. Platform features and supported versions change between releases, so confirm them against the version you run before making operational decisions.
Authoritative Sources
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.