Cloud Native and Automation at Garmin
summary
Garmin moves dozens of apps from VMs to Pivotal Cloud Foundry using Jenkins pipeline shared library to make deploys reproducible, but still lacks automated rollbacks and full CI acceptance tests. Production wins include the support portal and global SSO (migrated off many VMs to SSO on 2 CF instances per DC), junior devs shipping ten ERP microservices in a week, and logging moved to JSON for aggregation. Key metrics: 1100 deployments in December 2016. Plans: static security scans, config tweaks instead of runtime config reliance, and a Garmin Labs pairing environment.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:13About Garmin
- 1:16Garmins Cloud Native Journey
- 2:15Overview
- 2:39First Cloud Native Platform
- 5:25Automation
- 7:21Pipelines
- 8:48Support Portal
- 10:42Single SignOn
- 14:41Sesame Street
- 15:26Where are we
- 17:21Configuration
- 19:50Pipeline
- 20:53Garmin Labs
- 24:00Questions
related talks
49mAutomation in Deployment on Hybrid Hosting and Private Cloud Environments
31mPut Your Money Where Your CF Is
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
25mDevOps & Insurance Company
27mLessons Learned from Corelogic's Year of Agile Development with Cloud Foundry
16mDeployments We Can Believe In
26mCNCF Cross-Cloud CI Intro
32mLearnings from a DevOps Organization in the Making