The challenges of migrating 150+ microservices to Kubernetes

How do you decide whether to adopt a leading-edge technology? The Financial Times recently migrated its content platform to Kubernetes. Join Sarah Wells to find out what it takes to migrate 150+ microservices from one container stack to another without affecting the existing production users and while the rest of your teams are working on delivering new functionality.

If you adopt things at the leading edge, you can gain in the short term, but in the long term, successful technologies get commoditized and become easier to use. You don’t want to be running your own hand-rolled container platform when other people are using managed Kubernetes—the cost is likely too high. But how do you decide whether to adopt a leading-edge technology? And how do you know when it’s time to change? Finally, how can you migrate onto the new architecture while keeping everything up and running? The Financial Times content platform team put its first containers live in mid-2015 and migrated the rest of its services over by April 2016. At that point, the team was using a largely self-built stack on CoreOS Container Linux with Fleet to do cluster management. At the end of 2016, the team members decided they wanted to benefit from the work other people were doing and switched over to Kubernetes. But it’s not easy to do that kind of move when you have 150+ microservices and you need to keep the existing platform running in parallel while you do the migration. Sarah Wells explains why the team decided to do this migration, the challenges they faced in doing it while supporting their live platform, and the lessons learned along the way.