Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 37 ยท Getting Started

What Is Red Hat OpenShift?

Learn what OpenShift is, how it extends Kubernetes with builds, routes, security and a web console, and who uses it. Includes runnable stand-ins to explore the ideas.

Red Hat OpenShift is a platform for running containerized applications. It is built on Kubernetes, the open-source system that schedules containers across many machines, and it adds the pieces a company normally has to assemble by hand: a web console, a build system, a built-in image registry, secure defaults, an installer, over-the-air updates and a catalog of add-on software called Operators.

If Kubernetes is an engine, OpenShift is the whole car. You still drive with the same pedals (Pods, Deployments, Services), but the doors lock, the dashboard works and the maintenance schedule is handled for you.

Honest note about this track. OpenShift is a platform that needs a real cluster, so it cannot run inside your browser on this site. The <TryIt> blocks you will see are small Python programs that act as stand-ins: they model an idea (how a route picks a service, how a quota is checked) so you can experiment. They are labelled every time and they never claim to be real oc output. Commands shown in plain code blocks are real commands, but we only show output when we are sure what it looks like.

The problem OpenShift solves

Running containers on one laptop is easy. Running hundreds of them for many teams, safely, with updates and without downtime is not. A company that picks plain Kubernetes soon has to answer questions such as:

  • Which operating system do the nodes run, and who patches it?
  • How do developers get from source code to a running container?
  • How do users sign in, and what is each person allowed to touch?
  • How do we stop one team's container from reading another team's data?
  • How do we upgrade the cluster without a weekend of manual work?

OpenShift answers each of them with a supported, tested default. That is why enterprises, banks, telecoms and governments adopt it: they get one product with one support contract instead of thirty projects glued together.

What you get on top of Kubernetes

Area Plain Kubernetes OpenShift adds
Operating system Your choice, you patch it Red Hat Enterprise Linux CoreOS, updated by the cluster
Install and upgrade Many tools exist One installer and a built-in update mechanism
Web console Optional dashboard Full console for developers and administrators
Building images Not included Builds, Source-to-Image, Pipelines (Tekton)
Image registry Bring your own Integrated registry and ImageStreams
Exposing apps Ingress objects Routes with a built-in router
Security Opt-in hardening Security Context Constraints and restricted defaults
Extending Manual installs Operators and OperatorHub

Do not memorize the table yet. Each row becomes its own lesson. The point is the pattern: OpenShift takes something that is optional or missing in Kubernetes and makes it a first-class, integrated feature.

Kubernetes inside, OpenShift outside

Every OpenShift cluster contains a full Kubernetes. Almost every Kubernetes manifest you have seen works on OpenShift, and every Kubernetes API object such as a Pod or Service exists there. OpenShift adds extra API objects (Route, BuildConfig, ImageStream, Project) and extra controllers.

flowchart TB
  A["Your applications"] --> B["OpenShift platform services<br/>console, builds, registry, routes, Operators"]
  B --> C["Kubernetes<br/>scheduling, Services, storage API"]
  C --> D["Red Hat CoreOS + CRI-O containers"]
  D --> E["Servers: bare metal, VMs or cloud"]

Figure: OpenShift is a layered platform with Kubernetes in the middle.

Who uses what: three kinds of people

OpenShift has two main faces, and it helps to know which one you will see.

  1. Developers push code, watch builds, look at logs and open the application URL. They work mostly in one project.
  2. Administrators install and upgrade the cluster, manage nodes, set security policy and quotas.
  3. Platform engineers (a mix of both) build pipelines, templates and shared tooling.

The web console has a Developer perspective and an Administrator perspective for exactly this reason. This course covers all three jobs, beginning with the developer path.

A tiny mental model in code

Before touching a real cluster, here is a stand-in that models the layers above. It is not OpenShift; it is a lookup table that tells you which layer owns a feature.

Python Stand-in: which layer owns which feature?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Counting what a platform saves you

Here is another stand-in: a checklist of chores that a team must own when running Kubernetes by itself, and which of them OpenShift covers out of the box. The list is illustrative, not a benchmark.

Python Stand-in: chores a platform covers

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice the unchecked items. OpenShift does not design your application or pick every vendor for you. It lowers the amount of glue work, it does not remove engineering.

Where OpenShift runs

OpenShift runs almost anywhere: on bare-metal servers in your own data center, on virtualization platforms, and on the big public clouds. There are also managed versions where the provider operates the control plane for you. The next lesson compares these options and shows the free ways to try it.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is OpenShift built on?

    Every OpenShift cluster contains a full Kubernetes, and OpenShift adds builds, routes, security defaults, a console and Operators on top.
  2. 2. Which of these objects is specific to OpenShift?

    Route is an OpenShift API object for exposing services outside the cluster. Pod, Service and Deployment come from Kubernetes.
  3. 3. Why does OpenShift have a Developer and an Administrator perspective in the console?

    Developers mostly work with applications in a project; administrators manage nodes, updates and policy, so the console shows each group what it needs.
  4. 4. Which statement is true about this track's runnable examples?

    OpenShift needs a real cluster, so the examples here are clearly labelled stand-ins written in Python.

Summary

  • OpenShift is Kubernetes plus an integrated platform: console, builds, registry, routes, security defaults, updates and Operators.
  • Kubernetes objects still work; OpenShift adds objects such as Route, BuildConfig, ImageStream and Project.
  • It targets teams that want one supported product instead of assembling many parts.
  • The console has Developer and Administrator perspectives.
  • Examples in this track are labelled stand-ins because the real product needs a cluster.

Next: Editions and Ways to Run OpenShift