Eating Your Vegetables: How to Manage 2.5 Million Lines of YAML
Talkat KubeCon + CloudNativeCon North America 2020 Virtual · on Thursday, 2020-11-19· at 15:45· Intrado Virtual Event Platform,·
summary
Intuit manages about 2.5 million lines of YAML across ~200 clusters, ~2,500 Git repos and ~9,000 namespaces using GitOps and a Kustomize-centered workflow. The platform team distributes a versioned remote base that services inherit, each service owning a repo with a top-level base plus per-environment overlays, yielding ~270 lines per service and ~675,000 lines managed in git. Practical problems include heavy user support, automation to update 2,500 repos, Kustomize CRD limitations that forced a fork, and upgrade risk that can break many apps at once.
AI-written summary · about
chapters (10)
- 0:001 paloalto NETWORKS
- 5:24Considerations
- 6:14Developers • Building bespoke applications as a service • Focused on business logic, and less about platform Want to deploy early and often, don't care about semantic versioning
- 7:53Affects how you expose the platform to the user e.g. Abstraction v. RAW YAML
- 10:48Approaches
- 11:00Nothing to leam Disadvantages: • Zero configuration re-use (umaintainable)
- 11:51Disadvantages: • Templates become complex and unreadable Examples
- 13:04Mostly flexible Disadvantages: • Not immediately intuitive . Lack of parameterization makes many use cases harder than necessary
- 18:04Intuit Case Study
- 27:18#2 Automation & migrations • YAML is hard to 'upgrade • Thousands of pull requests
related talks
15mScaling your Organization with GitOps
29mTales from the Branches: GitOps in the Real World
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
46mFrom 1,000 to 5,000 Users: Scaling GitLab Without (Too Much) Pain
09mLightning Talk: How Intuit Enables GitOps at Scale For All Its Developers
29mThe Evolution of GitOps in Platform Engineering
19mWhen GitOps Is Not Enough
32mGitOps at Scale: Why Your Hub-and-Spoke Architecture is a Security Risk