# OpenShift

OpenShift is Red Hat's enterprise Kubernetes distribution — the same Kubernetes you already know, plus an opinionated set of developer, security, and operational tooling layered on top. This section covers what OpenShift actually adds, how to work with it day to day via `oc`, and the platform-specific concepts (Routes, S2I builds, Operators) that don't exist in a vanilla cluster.

## Read in this order

1. [What Is OpenShift?](<https://computecentral.in/kubernetes/openshift/01-what-is-openshift/index.md>) — how OpenShift relates to vanilla Kubernetes, Red Hat's distribution model, and OKD as the community upstream
2. [oc CLI and Projects](<https://computecentral.in/kubernetes/openshift/02-oc-cli-and-projects/index.md>) — `oc` as a superset of `kubectl`, logging in, and Projects as namespaces with more built in
3. [Routes and Networking](<https://computecentral.in/kubernetes/openshift/03-routes-and-networking/index.md>) — Route vs. Ingress, the built-in HAProxy router, and OpenShift's SDN/OVN-Kubernetes networking layer
4. [Source-to-Image and Builds](<https://computecentral.in/kubernetes/openshift/04-source-to-image-and-builds/index.md>) — S2I, BuildConfig, ImageStreams, and how `oc new-app` ties them together
5. [Operators and OLM](<https://computecentral.in/kubernetes/openshift/05-operators-and-olm/index.md>) — the Operator pattern, the Operator Lifecycle Manager, and OperatorHub as a catalog

> [!TIP]
>
> **Already know vanilla Kubernetes?**
>
> Most of what you already know transfers directly — a Deployment is still a Deployment. Focus on what's genuinely new: Projects, Routes, S2I builds, and OLM-managed Operators. Everything else is the Kubernetes you already have, with `oc` sitting on top of `kubectl`.

## Next

Continue to [Labs](<https://computecentral.in/kubernetes/labs/index.md>) to practice these concepts hands-on, including on OpenShift Local.
