Speaker
Description
Indico has been architected for being deployed to a production environment in the traditional way: a host machine (a a cluster of machines) running Linux and executing Indico and its dependencies as a constellation of systemd units. This is the approach currently officially documented and supported. Many organisations, including MaxIV Labs at Lund University, have moved or are in the process of moving towards cloud-native platforms and application ecosystems and are running Indico as a cloud-native application decomposed into several workloads, which are usually executing in Kubernetes environments. There is no officially supported, battle-tested and properly documented path of operating Indico and its dependencies in a Kubernetes environment yet, but we can work together to define one. I would like to talk about the journey to migrate Indico from a VM environment to K8S (OpenShift) at MaxIV Labs and about the challenges of orchestrating a cloud-native Indico production environment, such as automating the lifecycle management of Indico workloads.
