How to run like a startup with enterprise Kubernetes
summary
Scholastic moves hundreds of monolithic apps to OpenShift on AWS, standardizing on S2I, OpenShift templates, Jenkins, SonarQube, Artifactory, Prometheus, Fluentd and New Relic and running 200+ microservices in production. Time to market drops from two–three months to about two weeks; image bloat (1–1.5 GB) and long container startup times force smaller base images and resource limits. Infrastructure uses CloudFormation+Ansible bootstrapping, 3→5 infra nodes for router/monitoring resiliency, and plans to migrate to OpenShift 4 operators and Helm 3 for smoother upgrades.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:55Why are we here
- 3:18New technologies
- 4:11OpenShift
- 5:15Kubernetes Plus
- 6:34OpenChef
- 8:21Developer Productivity
- 9:24CICD Pipeline
- 9:56Enterprise Open Source Development
- 12:01Introduction to URI
- 12:18About Classics
- 12:44Challenges
- 13:32Monitoring and alerting
- 13:51Application deployment process
- 14:41Why Kubernetes
- 15:08Reduce time to market
- 15:19Gain consistency across CICD pipelines
- 15:59Why OpenShift on AWS
- 18:47How we set up the infrastructure
- 19:54Postbootstrap playbooks
- 20:48Basic architecture
- 22:07CICD pipelines
- 25:08Lessons learned
- 28:44Conclusion
- 30:15Demo
- 33:39Whats next
related talks
30mOpenShift: a Kubernetes Story in an Enterprise Environment
41mOpenShift: a Kubernetes Story in an Enterprise Environment
28mOpenShift for the Enterprise or What Could Possibly Go Wrong
47m101 - Deploy with OpenShift in an Enterprise Context
40mHarnessing the Power of Open Source for Cloud Native Developm...
01h 06mOpenShift - the power of Kubernetes for engineers
05mIGNITE: Kubernetes/OpenShift (in way too short of time)
22mOpenShift, or Kubernetes on steroids