← 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

📄 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.

💡 Answer

Choose Kubernetes for a flexible container orchestration foundation; choose OpenShift when you want an integrated DevOps and CI/CD platform with built-in workflows and tools.

🧠 AI Summary

Kubernetes runs and manages containers, while OpenShift builds an integrated platform on top of Kubernetes with build tools, automated workflows, operators, configurations, pipelines, security, monitoring, and deployment features. Kubernetes offers a flexible foundation but requires assembling and managing more of the platform. OpenShift is suited to teams that want a unified workflow from code push through pipeline execution, image creation, registry storage, and deployment across public cloud, private cloud, virtual machines, or bare metal.

🔑 Key Points

  • Kubernetes schedules, scales, and connects containers across a cluster.
  • OpenShift adds building tools, automated workflows, operators, and ready-to-use configurations on top of Kubernetes.
  • Standalone Kubernetes requires teams to manage pipelines, security, and monitoring tools themselves.
  • OpenShift integrates code pushes, pipeline execution, container image builds, image registry storage, and deployment through image streams.
  • OpenShift supports deployment on public cloud, private cloud, bare metal, and virtual machines.
  • OpenShift provides Ops teams with a web console for cluster management, resource monitoring, issue resolution, and scaling.

✅ Actionable items

  • Use Kubernetes as the base when the team wants to assemble and manage its own platform.
  • Use OpenShift when the team needs integrated build tools, workflows, operators, configurations, and CI/CD capabilities.
  • Configure a workflow in which a code push triggers a pipeline, builds a container image, sends it to an image registry, and deploys it through an image stream.
  • Use the OpenShift web console to manage the cluster, monitor resources, and resolve issues.
  • Scale applications by adding machines or running more pods of the same application.

🧭 Frameworks

OpenShift CI/CD workflow01:41
  1. A developer pushes code.
  2. The push triggers a pipeline.
  3. OpenShift runs the pipeline.
  4. The pipeline builds a container image.
  5. The image is sent to an image registry.
  6. OpenShift deploys the image through an image stream.

🧰 Tools & AI usage

  • Kubernetes — Runs, schedules, scales, and connects containers across a cluster.00:09
  • OpenShift — Provides an integrated platform built on Kubernetes with build tools, automated workflows, operators, configurations, pipelines, monitoring, and deployment capabilities.00:17
  • Linux — Operating system layer in the infrastructure stack.01:14
  • CentOS OS — Example operating system layer in the infrastructure stack.01:17
  • Image registry — Stores the container image built by the pipeline.01:52
  • Image stream — Deploys the prepared container image.01:57
  • OpenShift web console — Manages clusters, monitors resources, and helps fix issues in one place.02:10

⚖️ Advantages, risks & lessons

Advantages

  • OpenShift provides an integrated workflow instead of requiring separate tools.
  • OpenShift is flexible across public cloud, private cloud, bare metal, and virtual machines.
  • OpenShift gives Ops teams centralized cluster management, monitoring, issue resolution, and scaling.

Risks

  • Standalone Kubernetes can become complicated because teams must build the broader platform and manage pipelines, security, and monitoring tools.

Lessons

  • The platform choice should reflect whether the team wants a foundational orchestrator or an integrated DevOps platform.
  • An integrated platform can simplify the path from code push to production deployment.

💬 Quotes

With OpenShift, everything works together.

Captures the central benefit of OpenShift's integrated workflow.00:48

👤 People & companies

VMware

A deployment environment mentioned as part of the infrastructure stack.

01:09