Linux serverNETWORK ADMINISTRATIONSredhat

Kubernetes vs. OpenShift

Learn more about Kubernetes → https://ibm.biz/learnhub-kubernetes
Red Hat OpenShift on IBM Cloud → https://ibm.biz/OpenShift-on-Cloud
Check out the IBM Cloud Kubernetes Service → https://ibm.biz/kubernetes-service

OpenShift and Kubernetes are the most widely used container orchestration software options available today. Let’s take a look at the two solutions and how they relate and differ.

Get started for free on IBM Cloud → https://ibm.biz/sign-up-today
Subscribe to see more videos like this in the future → http://ibm.biz/subscribe-now

#kubernetes #containers #OpenShift

source

by IBM Technology

redhat openstack

20 thoughts on “Kubernetes vs. OpenShift

  • Why doesn't OpenShift come with LoadBalancer support? Services of type LoadBalancer are stuck in Pending state forever. Should paying customers really have to install projects like Metallb themselves and manage the lifecycle on their own?

  • I don't see the benefit of OpenShift on public clouds if you don't have a very large set of clusters to manager and you already run OpenShift in a private cluster and you're looking to streamline.

    Where OpenShift is a contender is where you need to run clusters on prem and especially if you don't already have a team of kubernetes experts in place. But IMO Red Hat should offer more out of the box to really stand out amongst the many alternatives. VMWare Tanzu doesn't look really mature yet and I don't think they have a huge uptake (I could be wrong) but I think they're heading in the right direction, especially in terms of CI/CD.
    Rancher is very interesting as well and have come a long way since they're humble beginnings.

  • Finally an explanation that actually answered my question. Large corporations have certain needs that are streamlined in Openshift.

  • Sorry guys, independent of what one might think about OpenShift, the claims of what is hard in vanilla Kubernetes are plain wrong. Good selling points for the overwhelmed CTO, though.

  • Excellent explanation sounds like something for Watson? Lol great videos folks.

  • Thanks for the explanation, I did some googling after seeing this and I don't see a big difference between Kubernetes and OpenShift. Some of the known issues in Kubernetes has been addressed in OpenShift but they are simple changes yet the main issue still exists, backend Pod communication though a bridged connection that's were the weakness is in this solution.

  • S2I if I understand correctly is github actions – but you get charged for it?

  • Better go with rancher and RKE2, you have more features than this and they are free!

  • Kubernetes support external load balancer too, like from AWS GKE and MS Azure.
    Rancher or kubeadmn updates the cluster very easy too.

  • You can do all the openshift features in kubernetes with few additional operators. Only potentially killer feature for OS is multicluster.

  • You’re outlining writing a Dockerfile as a pain point here, really ? I don’t think you sold s2i to anybody here, all developers nowadays write for containers as the new standard, am not sure where the problem in what you describes until min 3:00

  • as user of openshift and k8s, problem with openshift was that is soo big, that managing it was harder than using clear k8s

  • Are these "guardrails" hard rules?? If so then it limits flexibility of deployment.

  • "Openshift guards you from running around with scissors" – love it!

Comments are closed.