Hiden complexity of OpenShift Container Platform 4.1 scrutinised from the side of the 'Application Developer'

TL;DR Link to heading

Did you know that there are over 130 running pods needed to keep the OpenShift Platform 4.1 up and running? No. Neither did I.

OpenShift Container Platform from Dev Corner Link to heading

I’ve been working with OpenShift Container Platform for a while now. I’ve seen all the bright side of the 3.x version from the “application developer” side. As a DevOps guy, I never gave much thought about the complexity of the Platform. I am aware of the internals (Docker, Kubernetes, Registry, Router …) and have far understanding of API Objects like BuildConfig, Pod, Service, Route, ImageStream, PersistentVolumeClaim … For my daily work that’s all nice abstracted in YAML Object Definitions. A little more structured YAML template with all the objects and parameters and that’s it. As a template guru, with one blick I already see all the resources which will be created once the template will be processed. Even a few containers in DeploymentConfig specs didn’t give me shivers. I did it all, maintain code and configuration, improve CI/CD pipeline, migrate data in a persistent volume from one cluster to another or do any other related work implementing this new technology. I’ve never had a chance to see the Platform from the operations side, not until recently.

OpenShift Container Platform from Ops Corner Link to heading

I’ve stumbled upon information that version 4.1 can be installed on AWS. I’ve decided to give it a try. I’ve managed to deploy a cluster with the help of Red Hat’s Online Partner Enablement Network.

I’ve opened the door, got a glimpse from the other side, which gave me goose bumps. After the cluster installation, there were over 180 pods created and 133 in state Running.

Once you are aware of the complexity of the technology and all it’s moving parts, you are starting to realise why the customers are willing to pay to be insulated from that complexity.

Significant changes to the underlying architecture and installation process are applied in version 4.1, and many features from 3.x are now deprecated. Operators are the preferred method for creating on-cluster applications. Template Service Broker and OpenShift Ansible Broker will be deprecated.

That being said, I look forward to working with OpenShift Container Platform 4.1 in production. I believe that Red Hat and the community have done an excellent job with this release. OpenShift is one of the best PaaS on the market.