Working with a Kubernetes platform like OpenShift is different in many ways. It is not just the random delivery of a piece of software and putting it on a server. Working with OpenShift and accelerating innovation in your organization means that you have to think about many things: what your IT architecture looks like, how your organization and processes are structured and what your software looks like.
About the webinar
Azure Red Hat OpenShift enables you to deliver more often and quickly. Good that this is technically possible, but what do your internal processes look like? For example, do you still work with a change advisory board that must approve every change? Organizing your processes internally for this is key. But how?
In order to adapt processes, it is important to include your employees in the change, to train them and to develop (new) skills. You often see two sides: people who would like to cooperate and you have people who are a little less involved. Often, with a change like this, there is a need to take more responsibility and that is an exciting but exciting step. How do you deal with this as an organization? And to what extent does the responsibility lie with the management layer to facilitate this?
From OpenShift 4.6 it is also possible to work with virtual machines. In this way you pretend that a virtual machine is a container and then you can manage it in the same way. This offers all kinds of interesting possibilities, but there is also a risk: your employees can assume that software does not need to be modernized. What can you do about this?
- Rene Moddejongen – Open Source Lead – Microsoft
- Gert Jan van Halem – Chief Technology Officer – Devoteam Netherlands
- Stefan van Eijden – Microsoft Business Lead – Devoteam Netherlands