Years ago, the choice by default for microservices was Spring Cloud. There are thousands of systems where Netflix stack covers all microservices needs: configuration management, load balance, service discovery, obtaining secrets and much more. In the new era of clouds without vendor locks, the new default is Kubernetes. Container orchestrator out of the box covers a huge part of microservices concerns, but for use this, it is required to change the code and remove a couple of dependencies.
At our company, we recently transferred tens of systems to the new approach. Each team has chosen its most comfortable way. This talk will observe moving strategies, problems that need to be taken into account, and our experience in choosing the most optimal ride to Kubernetes.