How to develop apps on K8s and not die trying
summary
Kubernetes development is fragmented but solvable with concrete workflows: examples include Jib for Java image builds, Helm for templates, and the k14s suite (ytt, kbld, kapp) to template, build, and deploy. Demo shows minikube, local registry, kbld building images and pushing them, ytt applying overlays to change only the ingress or replica count, and kapp prompting and waiting for rollout. Claim is that composable, single-purpose tools that share the same configs speed the inner loop and can extend to CI/CD outer loops.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 0:24Developers
- 1:09Operations
- 2:16Kubernetes Ecosystem Engineers
- 3:33The disconnect
- 5:16Definitions
- 5:28Application
- 5:43Monolithic
- 6:35External Services
- 7:19Finishing
- 9:15Logical vs Physical
- 10:29Containers
- 11:59Application definition
- 12:20Application labels
- 14:12Customer resource definition
- 15:26Custom security definition
- 17:26Container Native Application Bundles
- 19:08Open Application Model
- 20:24Example Implementation
- 21:53Application Development Stages
- 22:03Application Development Cycle
- 23:21Tools
- 24:39MiniCube
- 32:51Openshift
- 33:43Deploy
- 41:41Build Images
- 45:56Inner Loop vs Outer Loop
- 46:41What we want
- 47:14How is this implemented
- 47:42Space
- 53:08Conclusions
- 54:06Consistency
- 54:41Quote from the future
related talks
17mtalk Kubernetes with
42mKubernetes native development workflows
01h 00mJava on Kubernetes What I Wish I Knew First
02h 18mDevelop and Deploy to Kubernetes like a Googler
14mKeynote: Kubernetes is Still Hard (for Developers)
45mKubernetes Local Development Workflow Distilled
54mClosing the Developer Experience Gap in the Kubernetes Ecosystem
41mBuilding Apps in Kubernetes: The Unforgiving Sea of...