Simplifying software development with Kubernetes and containers
summary
Verizon describes moving hundreds of services into containers on Kubernetes to standardize stacks, speed CI/CD and cloud migrations, and cut infrastructure cost by about 20% cost reduction. Teams share a single cluster with shared multi-tenant clusters and namespaces rather than provisioning per-team VMs. Training uses an inner-sourcing training model (internal StackOverflow, Hangouts, reusable libs). Migration pain points are learning curve and developer buy-in; operational shift includes moving from SLA to SLO and collaboration with Google on SRE practices.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:20Impact of containers on technology teams
- 1:40Impact of containers on DevOps
- 2:33Challenges
- 3:31Learning curve
- 5:03Public clouds
- 5:53Training
- 6:41Cost benefits
- 7:50resiliency
related talks
29mAccelerate AppDev with KIK (Kubernetes-Istio-Knative)
05mMoving to Kubernetes, or not?
46mAround & After Kubernetes: The Principles and Ideas that Guide Us
31mKubernetes Quick Wins and Migration Best Practices: RingCentral Example
38mBuilding the Perfect Infrastructure with Kubernetes
35mKubernetes journey
43mCloud Native - effective computing at scale
20mKeynote: The Challenges of Migrating 150+ Microservices to Kubernetes
