OpenShift and Kubernetes have evolved significantly since their beginnings in 2011 and 2014 respectively. The presentation discusses the past, present, and future of OpenShift and Kubernetes, including how they have grown large developer communities and are used by over 1,000 companies. It also outlines continued focus on multi-cloud management, standardization of tools like Tekton and Knative, and potential future directions such as simpler cluster operations, integration with GPUs and VMs, and stronger developer workflows.

1. OpenShift Evolution: Past, Present and
Future
Olaf Meyer
Senior Consultant
22.10.2019

2. OpenShift Evolution: Past, Present, Future Folie 2
Agenda
• Where do OpenShift and Kubernetes come from & what makes them special?
• What is happening in the community?
• A look into the crystal ball to see what the future might bring

3. OpenShift Evolution: Past, Present, Future Folie 3
Where do OpenShift and K8s come from & what makes them special?
• 2011 OpenShift 1.0
• 2013 Docker 1.0
• 2014 Kubernetes 1.0
• 2015 OpenShift 3.0
• 2019 OpenShift 4.0 Operator Framework, Multi-cluster Manager, Knative, Service Mesh, …

4. OpenShift Evolution: Past, Present, Future Folie 4
Where do OpenShift and K8s come from & what makes them special?
• OpenShift 3.3  CI/CD based on Jenkins, A/B Deployment
• OpenShift 3.4  Storage Quota, Job API, Dynamic Storage for public clouds
• OpenShift 3.7-  Service Broker, Network Policies
• OpenShift 3.11  CRIO, Istio (Tech Preview), Prometheus Metrics and Alerts
• OpenShift 4.0  Operator Framework, Multi-cluster Manager, Knative, Service Mesh, …

5. OpenShift Evolution: Past, Present, Future Folie 5
Difference OpenShift vs Kubernetes
OpenShift is based on Kubernetes and offers services and enhanced security out of the box
https://medium.com/preply-
engineering/k8s-auth-a81f59d4dff6

6. OpenShift Evolution: Past, Present, Future Folie 6
Who is using OpenShift?
More than 1.000 OpenShift customers

7. OpenShift Evolution: Past, Present, Future Folie 7
Now
• Cloud Foundry powered by Kubernetes
• Docker Swarm (Option to run container on Kubernetes)
• (Apache Mesos)
• OpenShift
• Google Kubernetes Engine (GKE)
• Amazon Elastic Kubernetes Service (Amazon EKS)
• Azure Kubernetes Service (AKS)
PaaS systems previous and now
Previous
• Cloud Foundry
• Docker Swarm
• Apache Mesos
• OpenShift

8. OpenShift Evolution: Past, Present, Future Folie 8
Statistics
Top projects Octoverse statistics 2018
(Source: https://octoverse.github.com/projects#repositories)
Total numbers
There are many more projects that are building on
top of Kubernetes/OpenShift
Name Commits Releases Contributors Repos.
Visual
Studio Code
55.130 136 975 165
React-nativ 18.161 329 2023 15
Tensorflow 68.706 94 2219 84
Kubernetes 83.717 561 2296 70
OpenShift
(Origin)
30.765 72 361 405
Docker CE 46.155 110 1992 138

9. OpenShift Evolution: Past, Present, Future Folie 9
What makes K8s special?
There are very large ecosystems of frameworks and applications that are using K8s
• Helm  “Package manager for Kubernetes”
• Spinnaker  “Cloud native Continuous Delivery”
• Istio  Advanced routing between container
• Knative  Deploy and manage modern serverless workload
• …
In general: For almost every application you can find an example how to run it on K8s

10. OpenShift Evolution: Past, Present, Future Folie 10
What makes K8s special?
It is used and therefore properly tested by a lot of companies
It is starting to become a catalyst to standardize frameworks and tools
• Container Runtime Interface (CRI)
• Container Networking Interface (CNI)
• Container Storage Interface (CSI)
• …
Deployment and running applications on K8s is relatively easy

11. OpenShift Evolution: Past, Present, Future Folie 11
What makes K8s special?
The installation of Kubernetes is another story…

12. OpenShift Evolution: Past, Present, Future Folie 12
What is happening in the community?
• Focus on management of multi/hybrid cloud
• Standardize build flow in Kubernetes with Tekton
• Standardize Serverless execution in Kubernetes with Knative
• Istio and Service meshes

13. OpenShift Evolution: Past, Present, Future Folie 13
Look in the crystal ball to see what the future might bring
With respect to the clusters:
• Simpler and more robust installation und updates of Kubernetes and OpenShift
• Run more than one cluster and possibly with more then one cloud provider
• Simpler scaling of nodes in cluster to reduce costs
• Also starting of pod without nodes i.e. AWS Fargate
• Integration with GPU to support ML and AI
• Run VM’s in an K8s/OpenShift cluster

14. OpenShift Evolution: Past, Present, Future Folie 14
Look in the crystal ball to see what the future might bring
With respect to applications of frameworks
• Operators to install, update and delete applications
• Serverless (not necessary FaaS) application to reduce costs
• Stronger integration of Istio or Services Meshes to have flexible routing without changes in
source code

15. OpenShift Evolution: Past, Present, Future Folie 15
Look in the crystal ball to see what the future might bring
With respect to the developer
• Tekton to build application in Kubernetes
• Run developer workspaces in the cluster with Eclipse Che
• Alternatives to Docker as runtime and to build container like podman

16. OpenShift Evolution: Past, Present, Future Folie 16
Look in the crystal ball to see what the future might bring
With respect to Operating Systems
• Kubernetes/OpenShift run native Windows pod/container

17. Any questions?

18. Thank you very much!

19. ConSol
Consulting & Solutions Software GmbH
St.-Cajetan-Straße 43
D-81669 München
Tel.: +49-89-45841-100
info@consol.de
www.consol.de
Twitter: @consol_de