November 27, 2019

251 words 2 mins read

Lessons Learned From Maintaining Continuous Delivery While Migrating From a Static Infrastructure to Kubernetes [B]

Lessons Learned From Maintaining Continuous Delivery While Migrating From a Static Infrastructure to Kubernetes [B]

Finn.no is Norway's largest website. Whilst running on static infrastructure, we support 300 microservices, 1400 deploys a week, and 6 minutes from git push to production. But our platform didn't meet …

Talk Title Lessons Learned From Maintaining Continuous Delivery While Migrating From a Static Infrastructure to Kubernetes [B]
Speakers Audun Fauchald Strand (Team Lead - Platform and automation, NAV - Norwegian Welfare Administration)
Conference CloudNativeCon + KubeCon Europe
Conf Tag
Location Berlin Congress Center
Date Mar 28-30, 2017
URL Talk Page
Slides Talk Slides
Video

Finn.no is Norway’s largest website. Whilst running on static infrastructure, we support 300 microservices, 1400 deploys a week, and 6 minutes from git push to production. But our platform didn’t meet the demands of our developers. So we started to migrate our platform from static servers to a dynamic approach, both on premise and in the cloud. We are not yet done with that process, but we have learned a lot. We want to share these learnings with you The talk will maintain the following parts:

Introduction to FINN, and its legacy infrastructure How we set up kubernetes, and how this has changed in the last 6 months On-premise vs GKE Tools we made for easier deployment and migration FIAAS (Tool for deploying apps with a minimal config for each app) HA proxy ingress controller for migrating app traffic How to integrate Prometheus and Kubernetes for painfree metrics Experiences Migrating apps are difficult Kubernetes is complex Developers like to make apps quickly Monitoring is everything

comments powered by Disqus