Tales of Serverless
summary
Minimal knative service YAML expands into many Kubernetes objects automatically, demonstrated by applying one file and watching deployments, services, autoscalers and routing appear. The system scales-to-zero by default and an activator buffering proxy fronts cold starts so HTTP requests trigger pod spin-up and are forwarded when ready. Eventing uses CloudEvents to Kafka via Brokers and Triggers; demo shows a Go app sending HTTP CloudEvents to a broker, getting accepted (202) and delivered to the consumer.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:23Developer Knight’s quest
- 2:27Simplifying deployment with K native
- 5:22Finance Dragon encounter
- 6:26Scaling to zero
- 9:40K native scaling behind scenes
- 12:30Policy ogre and Kafka
- 13:34Eventing with CloudEvents and Kafka
- 20:19Princess rescue with Kafka
- 22:29Summary and K native benefits
- 23:56Q&A
related talks
48mEvent-driven serverless architectures using Knative and Cloud Run.
57mServerless with Knative
35mStop Calling Knative Serverless!
23mServerless with Knative
31mBeyond Traditional DevOps: Dive into Serverless with K8s
55mServerless On Your Own Terms using Knative
52mServerless with Knative
01h 09mTutorial: Cloud-Agnostic Serverless
