Today, Kubernetes is the defacto standard if you want to run container workloads in a production environment, though that wasn’t always the case.

We had have a fair amount of monolithic code for our products and to make sure we could build Central Repository in a way that would be easier to manage at the scale we needed to make changes. For us, that meant changes to the way we write code (more Go), how we build apps (using Docker and Kubernetes), and how we deploy (using Helm).
We had to figure out a whole bunch of things as we looked at building proper microservices that we could deploy to Kubernetes.

During the session, we will pay special attention to things like persistence, resource limits, affinity and probes because containerizing an app is not simply putting your existing app into a docker container.