Is OpenShift Worth Learning If You Already Know Kubernetes?

Not everywhere requires OpenShift skills. It's mostly seen in corporate enterprise environments. Many startups and SaaS companies stick to standard Kubernetes because it suits their needs better. So depending on the industry, OpenShift may not be necessary.

You might face hurdles with OpenShift if you don't have experience with it. I recently missed out on an opportunity because I lacked OpenShift experience, despite having worked with other Red Hat products and EKS. It does have a managed control plane similar to EKS or AKS, but the regular version can give you more control. It's frustrating when candidates are evaluated so heavily on OpenShift skills!

If you're already familiar with Kubernetes, transitioning to OpenShift shouldn't be too tough. Think of OpenShift as a more feature-rich version of Kubernetes, offering a lot of customized options that you won’t find in standard setups like KubeADM or Rancher. The key is to dive into the documentation as you use it in practice; that's the best way to learn its unique aspects.

Is it enough to just start learning the 'oc' commands instead of going through the entire OpenShift curriculum? That’s a good question!

I respectfully disagree. OpenShift is a highly opinionated version of Kubernetes with significant customization that can make it challenging to learn. The documentation isn't as helpful as it should be, and you may find yourself struggling to grasp its nuances. While it can do amazing things, it does have its quirks that can trip you up if you're not careful.