One of the things to notice is that this product can be expensive. Another thing is that OpenShift has its own CLI, it has features in it that you don't have under normal Kubernetes. So if you're just a plain Kubernetes developer, you either don't know about these other features and you don't take advantage of them so you're basically treating it like a normal Kubernetes or there's a slight learning curve as you start to learn how the new CLIs work, the other options that are not available in Kubernetes. There is a learning curve; it's not high, but it's still there. That's another negative against OpenShift. If you're purchasing OpenShift on their OpenShift container platform, you will have to manage the master nodes. If you are using Kubernetes in AWS, Google, and Azure, you don't manage master nodes. It's not really a big deal. It's all part of the patching in OpenShift. People will start to say, "Well, I don't want to manage the masters." But I think if they actually see the process of patching an OpenShift, they would say, "Okay, it's not even worth arguing because it's so simple." Alternatively, the main three cloud vendors can provide OpenShift as a service.
