06-15, 12:30–13:05 (Europe/Prague), D105 (capacity 300)
Since the beginning of time, declarative APIs have been driving everything that can happen inside an OpenShift cluster. Predefined CRDs, operators defining custom CRDs, everything is about declarative APIs. Write your YAML once, deploy it, forget it. That’s how you create a cluster, that’s how you deploy your workload.
But is it, for real, as simple as it sounds? How do you bring declarativeness to the imperative world? In the current state of things, host networking is one huge imperative nightmare. So how to happily marry an old-school Network Manager and brand new Kubernetes API? In this session we will demonstrate how NMState provides you with a Declarative Network API, finally allowing you to manage host networking in a declarative manner.
To make it more entertaining, we will show you how the OpenShift cluster with NMState Operator manages networking on the nodes it deploys. It may sound like a chicken and egg situation, but trust us, it is not. Last but not least, we show how it protects itself from applying destructive network changes potentially taking your cluster down.
Join us and create the most complex network topologies on the fly.
Principal Software Engineer at Red Hat, where he is currently working at the OpenShift Bare Metal Networking team. He is creating solutions that enable distributed computing in environments where cloud providers are not enough, demands are tough and direct access to the hardware is a must.
In the past worked at CERN on cloud and bare metal projects that were powering the Large Hadron Collider, and afterwards at ETH Zurich as part of the team doing research in the network security and internet protocols area.
Ben has worked in cloud for over 10 years, first as a member of the OpenStack common libraries and deployment teams, and most recently as part of the on-prem networking team for OpenShift.