Michelin, 120 Years Old, Moved to IaC
summary
Michelin migrated its infrastructure management to Infrastructure as Code across 80 production sites and about 14,000 VMs, exposing inventories via the DCX/dcatrix portal APIs. Engineering implemented Azure landing zones using ARM templates, Terraform modules, GitLab pipelines, Backstage templates and automated Kubernetes cluster provisioning, with GitOps pilots for cluster and infrastructure reconciliation to deliver reproducible, self-service infrastructure and automation gains while platform teams retain most operational ownership.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:34Pre-2015 issues
- 8:082015 state of play
- 11:58Early cloud initiatives
- 16:09Cloud exploration and review
- 19:56Shift left and platforms
- 24:09Team transformation and automation
- 29:01Cloud and Kubernetes
- 31:05Cloud-native golden paths
- 34:52Backstage and project acceleration
- 36:16Training and technical expertise
- 37:58Conclusion and resources
- 38:21Q&A
related talks
40mInfrastructure as code in action - How we built a platform during a cloud migration
23mA Journey to Automated Infrastructure
53mInfrastructure as Code in Action! How to Build a Cloud Platform
40m“So, where do you put IaC of your services?”
15mInfrastructure as a Code: Best Practices and Myths
34mIaC – Improving and Securing Infrastructure Provisioning in the Cloud
25mInfrastructure Tasks in the Company
50mInfrastructure-From-Code and the end of Microservices