Containing the Container: Developer Experience vs Strict Security Posture
Talkat KubeCon + CloudNativeCon North America 2019 · on Tuesday, 2019-11-19· at 10:55· Room 29ABCD - San Diego Convention Center, Upper Level·
summary
Verizon runs 2000+ apps across on‑prem, multi‑cloud and edge clusters with 80,000+ workloads and 300k+ deployments in 90 days and security policy forbids no Docker daemon locally. The applied solution uses Jib for Java image builds (no Dockerfile needed), Kaniko via GitLab runners to build Dockerfile images in-cluster, Skaffold to automate local edit→build→deploy loops, Harbor + Clair to scan and quarantine images, and Octant/K9s for debugging; remote Docker-in-Docker proved slow, costly, and jurisdictionally risky.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:36Who are we
- 2:07Digital Transformation App Modernization Strategy
- 4:47Challenges
- 7:04Problems
- 7:45Redefining Developer Tools
- 10:08GitLab Demo
- 10:55Run Part
- 11:29Prerecorded videos
- 12:21Getting started
- 12:52Deploying
- 13:12Maven
- 14:45Scaffold
- 15:29Scaffold Dev
- 17:13Kaneko
- 17:58Scaffold config
- 18:58Scaffold run
- 23:32Demo
- 24:03Next Steps
- 24:29Harbor
- 25:35Vulnerability Graph
- 26:26Replications
- 28:34Currents Dashboard
- 29:33Coope
- 30:44Summary
- 32:01Questions
related talks
34mHow to Contain Security in your Containers
47mContainer Security, Are You Doing It Wrong?
46mA Security State of Mind: Continuous Security with Kubernetes
18mPractical End-to-End Container Security at Scale
08mInterview
43mContainer Security: So Many Options, Use Them All!
05mContainer Security Best Practices
36mContainer Security Made Easy – Tools and Techniques for Developers