A Thin Line Between Love and K8s
summary
Kubernetes provides an open control loop that constantly reconciles a control loop desired-state and an extensible API ecosystem of monitoring, CI/CD and security tools, but a Novant Health case study shows implementation often fails for lack of people and changed processes: small IT footprint, COTS stateless apps that didn’t fit VM-based Tondu infrastructure, and no Kubernetes SMEs led to delays and partial adoption. Measure ROI and flow metrics, track vulnerability response and usage, and treat integrations as experiments before wide rollout.
AI-written summary · about
chapters (10)
- 0:00Introduction and speakers
- 1:30Containers vs VMs explained
- 4:23Kubernetes control loop and API
- 6:50Love-hate relationship with K8s
- 7:11Digital transformation with K8s
- 8:58Novant Health case study
- 10:40Measuring K8s success metrics
- 13:26Future state drives innovation
- 14:08Summary and key takeaways
- 16:32Q&A session
related talks
14mLessons from the Kubernetes Adventure
21mKeynote: In Search of the Kubernetes "Rails" Moment
14mEverything Worked Before Kubernetes
30mKubernetes: Fad or Real Benefit?
03mKeynote: Time to Unlock the Edge Potential at Scale
40mKubernetes is Your Cloud Control Plane
11mKeynote: Stitching Things Together
07mKeynote: Pushing the Boundaries of Open Source for a Brand New Edge