Kubernetes is an open source project (or even a framework), while swimming cap best OpenShift is a product that comes in many variants. There s an open source version of OpenShift which is called OKD . Previously it was called OpenShift Origin, but some  clever folks at Red Hat came up with this new name which supposes to mean  The Origin Community Distribution of Kubernetes that powers Red Hat OpenShift (?). But let s forget about names for a while and focus on what are implications of that.

For someone coming straight from Kubernetes world who used Helm and its charts, OpenShift templates as the main method of deployment whole stack of resources is just too simple. Helm charts use sophisticated templates and package versioning that OpenShift swimming cap amazon templates are missing. It makes deployment harder on OpenShift and in most cases you need some external wrappers (like I do) to make it more flexible and useful in more complex scenarios than just simple, one pod application deployments.

No more manual actions for swimming cap girl issuing and renewal of certificates and additionally you can use trusted CA for free thanks to integration with Letsencrypt !Similarly like with Ingress, OpenShift chose to have a different way of managing deployments. In Kubernetes there are Deployment objects (you can also use them in OpenShift with all other Kubernetes objects as well) responsible for updating pods in a rolling update fashion and is implemented internally in controllers. OpenShift has a similar object called DeploymentConfig implemented not by controllers, but rather by sophisticated logic swimming cap kids based on dedicated pods controlling whole process.

It has some drawbacks, but also one significant advantage over Kubernetes Deployment - you can use hooks to prepare your environment for an update - e.g. by changing database schema. It s a nifty feature that is hard to implement with Deployment (and no, InitContainers are not the same, as it s hard to coordinate it with many instances running). Deployment, however, is better when dealing with multiple, concurrent updates - DeploymentConfig doesn t support concurrent updates at all and in Kubernetes you can have many of them and it will manage to scale them properly.

Now this is something that I really miss in Kubernetes and personally my favourite feature of OpenShift. ImageStreams for managing container images. Do you know how  easy it is to change a tag for an image in a container registry? Without external tools such as skopeo you need to download swimming caps target the whole image, change it locally and push it back. Also promoting applications by changing container tags and updating Deployment object definition is not a pleasant way to do it.

Red Hat created OpenShift long before Kubernetes project was found and from the start, it was a PaaS platform. By switching from their custom solution (they used something they called gears instead of containers) to Kubernetes it became easier to bring more features and one of the most exciting is integrated Jenkins. There are multiple CI/CD software solutions available, but Jenkins is still the biggest, most universal, generic and mature solution.