How ING Accelerated Kubernetes Deployments Across 500+ Apps
summary
ING standardizes on an internal container hosting platform (an OpenShift cluster offering namespace-as-a-service) and YAML templates that enforce non‑negotiables (two replicas, node anti‑affinity) while letting teams set sizing and config. Templates auto‑version and mostly auto‑update; about 600–700 apps are now in production and thousands of engineers onboard with a few clicks. A custom pipeline monitoring system collects telemetry and template usage, surfacing failures and obsolete versions so fixes and policy changes roll out once to everyone.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:07ING scale and Kubernetes challenges
- 3:30Why Kubernetes feels difficult
- 4:14Organizational side of cloud adoption
- 7:04Technology adoption model
- 9:50Spotted phase opportunities
- 11:36Top-down challenge multiple clouds
- 13:40Bottom-up challenges automation
- 16:27Middle-out strategy
- 17:31Pilot phase user-driven validation
- 19:18Standardizing cloud pipelines
- 20:43Benefits of centralized complexity
- 22:30Build it phase scaling automation
- 23:52Scale it phase stabilizing support
- 25:40Operated phase reliability focus
- 26:43Lessons learned and takeaways
- 28:06Q&A templating and customization
- 29:31Q&A template versioning
- 30:31Q&A monitoring usage
- 31:54Q&A lifecycle and decommissioning
related talks
34mContainer Hosting Journey
29mSo you think you can mesh? Scaling ING's service mesh
36mHow to run like a startup with enterprise Kubernetes
46mThe Journey of Migrating 2500 Apps to Multi-Cluster Kubernetes and Zero Trust Istio
29mAccelerate AppDev with KIK (Kubernetes-Istio-Knative)
46mAround & After Kubernetes: The Principles and Ideas that Guide Us
53mDeploying to Kubernetes Thousands of Times Per/Day
35mKubernetes journey