← All transcripts

Kubernetes vs. OpenShift: Choosing DevOps and CI/CD Workflows Transcript, AI Summary & Key Points

IBM Technology · Jun 07, 2026 · Education · 03:01 · EN

Watch on YouTube

AI Summary

Kubernetes runs, schedules, scales, and connects containers across a cluster, while OpenShift builds on Kubernetes with platform capabilities such as building tools, automated workflows, operators, and ready-to-use configurations. Running Kubernetes alone requires teams to build and manage the broader platform, including pipelines, security, and tools. OpenShift integrates code pushes, pipelines, container image builds, registry storage, image-stream deployment, cluster management, monitoring, issue resolution, and scaling into one platform. It can run across public cloud, private cloud, bare metal, and virtual machines.

Key Points

  • Kubernetes schedules and scales containers and keeps them connected across a cluster.
  • OpenShift builds on Kubernetes with building tools, automated workflows, operators, and ready-to-use configurations.
  • Running Kubernetes on its own requires teams to build the entire platform and manage pipelines, security, and tools.
  • OpenShift can run on public cloud, private cloud, bare metal, and virtual machines.
  • A code push can trigger an OpenShift pipeline that builds a container image and sends it to an image registry.
  • OpenShift deploys a ready container image through an image stream.
  • OpenShift provides a web console for cluster management, resource monitoring, and issue resolution.
  • Scaling can involve adding more machines or running more pods of the same application.
🔒 Full analysis locked

Unlock more videos and the full analysis

A credit unlocks one video's full analysis for good — the build steps, the tools and how each was used, the methods behind every use case. Pro opens the whole library instead, and raises how many videos you can analyse a day.

Unlock full analysis — free

Transcript

Searchable transcript of Kubernetes vs. OpenShift: Choosing DevOps and CI/CD Workflows — IBM Technology (03:01). Search for a phrase, then click its timestamp to jump straight to that moment in the video.

Captions sourced from the original video on YouTube, published by IBM Technology. The video, its captions and all related intellectual property remain the property of their respective owners; AINotes claims no ownership. Provided for research, accessibility and search — see the Transcript Notice and Copyright Policy.

00:00 Kubernetes, OpenShift. Kubernetes, Openshift. Which one do you actually choose? I'm going to make it simple for you right now. Kubernetes runs your containers, it schedules them, scales them, and keeps everything connected across the cluster. OpenShift builds on top of that. It takes Kubernetes and add a full platform, building tools, automated workflows, operators, and ready-to-use configurations.

00:27 So you're not just starting from scratch. Running Kubernetes on its own is not just running an application. You're building the whole entire platform. You manage pipelines, you handle security, you deal with emission tools. So things can get complicated. Now think about it. With OpenShift, everything works together. Code gets pushed, pipeline starts, the app goes live.

00:55 One simple flow, not a mix of separate tools. Now the exciting part, where it all comes together. Let's start from the base. So we have public cloud. We have private cloud. We have VMware and bare metal. And on the top of that, we have our operating system. Let's say Linux, or Centos OS. And then the core Kubernetes. And we got OCP, which is OpenShift.

01:30 One big advantage is the flexibility. OpenShift can run on any of these. Private, public cloud, bare metal, virtual machine. Let's switch gears. You have a dev team that writes code, pushes it. That push triggers a pipeline. OpenShift runs the pipeline. Builds a container image and sends that image to the image registry. Once the image is ready, OpenShift takes that image and deploys it through something called image stream.

02:06 Now on the other side, the Ops side. The Ops team, OpenShift provides a web console for them as they can manage their cluster, monitor resources and fix issues all in one place. Also scaling. So when it comes to scaling, they can add more machines when needed or they can run more pods or of the same application. Those are pretty much simple. You're not just deploying applications, You're building a system that can team and monitor through it.

02:39 And once the system is in place, everything becomes easier. So let me ask you this, is your platform helping you move faster or slowing you down? Let me know in the comments and if you have any questions, feel free to ask.