Container Hosting Journey
summary
ING runs a multi-tenant namespace as a service on OpenShift 4.10 using a Python project controller built on a custom python operator framework and an orchestration engine of sequential stages with concurrent units. A quota autoscaler watches namespace ResourceQuotas, mutates dev/test pod requests to 10m, and auto-increases quotas; that change cuts allocated CPU in resource quotas from ~9,000 cores to ≈1,700 (≈7,600 cores saved) and saves ~500 cores via mutation. Platform serves 2,000+ namespaces (~5,000 pods per environment) in production and will open-source the autoscaler, operator framework, and orchestration code.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:17Agenda
- 5:08Use Cases
- 6:20What is a namespace
- 7:27Components
- 9:12Applications
- 9:36Cloud Portal
- 10:13Project Controller
- 11:05Scaffolds
- 12:40ICE HP API
- 13:38Steps
- 15:18Code
- 15:54Quota Autoscaling
- 17:54Quota Scalar
- 18:37Metrics
- 21:25Port Research Mutator
- 21:40Demo
- 24:52Open Source
- 26:12Questions
related talks
33mHow ING Accelerated Kubernetes Deployments Across 500+ Apps
29mSo you think you can mesh? Scaling ING's service mesh
36mHow to run like a startup with enterprise Kubernetes
28mOpenShift for the Enterprise or What Could Possibly Go Wrong
41mOpenShift: a Kubernetes Story in an Enterprise Environment
24mIstio in Production: Expected Value, Results, and Effort
52mOperating OpenSearch at Scale: Lessons From Managing 10,000+ Clusters Across...
44mPerformance and Scalability Tuning Kubernetes for OpenShift and Docker