Paradox Of Choice: How To Pick an Application Definition That Works For You!
summary
Intuit evaluates Helm, Kustomize (KRM plugins), KubeVela and Crossplane with POCs and a weighted scorecard across learning curve, effort, GitOps fit and operational surface. The environment runs about 6,000 developers across ~2,000 services and ~2,245 clusters, so the chosen path must scale. The outcome picks a Kustomize KRM plugin that generates Kubernetes manifests from an OAM-style app.yaml, syncs via Argo CD integration, hides cloud/k8s complexity, supports trait overrides like vertical sizing, and proves practical in demoed deploys.
AI-written summary · about
chapters (8)
- 0:00Introduction to the problem
- 1:03Infrastructure landscape
- 3:44Key developer challenges
- 6:31Evaluating solutions
- 9:12Assessing tools and frameworks
- 15:03Data-driven selection
- 19:50Implementation demo
- 24:53Takeaways and Q&A
related talks
29mK8s Complexity Tamed: One Interface To Rule Them All With CNCF Incubat...
26mFive Hundred Twenty-five Thousand Six Hundred K8s CLI’s
34mChoose Your Own Adventure: The Dignified Pursuit of a Developer Platf...
55mHow to develop apps on K8s and not die trying
28mThe Building Blocks of DX: K8s Evolution From CLI to GitOps
14mKeynote: Kubernetes is Still Hard (for Developers)
15mChoice is great, but not having to choose is better
24mIf Your Application is Going to Run in a Multi-Node Cluster, Why Are You Develo...