Top7 decisions a DevOps Architect will need to face when running kubernetes in high scale.
So you decided to take the red pill and run your containerised applications on Kubernetes. Day 0 looks fantastic. You deploy, scale, and monitor. Then Day 1 and Day 2 arrive. Day 3 is around the corner. You suddenly notice that Kubernetes is a Microcosmos. You are challenged to take architectural decisions. How many clusters should I create, how big? Which tenancy model should I use, SILO? multi? How do I connect services across clusters? Join me in this session where I will present a few of those key decisions that I discuss daily with my strategic customers.
Kobi has been working for 9 Years at AWS, spending most of the time as a solution architect working with myriad of customers, consulting and leading technology partners. Now-days he is practicing his passion for container technologies and works as a container specialist solution architect helping customers and partners to modernize, migrate and design large scale containerised environments. I focus on container networking, multi-cluster & service discovery. In my line of work I mainly interact with strategic customers. Been in the cloud since 2013.