Governing the Cloud Native Event Bus: Applying ServiceMesh to Knative Eventing Workshop (Part 2)
summary
Demo wires Camel K producers into Knative Eventing channels backed by Apache Kafka, showing timers emitting messages, subscriptions consuming and forwarding, and messages visible as Kafka topics. Service mesh (Istio) provides mTLS, centralized authz hooks and observability via Kiali and Jaeger so traces and service graphs show real pub/sub flows. Namespace-level multi‑tenancy lets different channels use Kafka/NATS/in‑memory. Demo runs end‑to‑end with pods scaling (including scale‑to‑zero), but requires deliberate CR and mesh wiring.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:10Demo
- 1:05Knative Services
- 4:52Apache Camel
- 7:20Event Sync
- 11:59Wrapup
- 15:30External Authorization
- 17:25GitHub Issues
related talks
01h 02mModern Event-Driven Workloads with Knative
32mKnative Eventing Installed Then What Next?
48mLet's Go Knative
25mAchieving a Highly Available and Scalable Multi-Tenant...
26mService Mesh, Serverless and Event Drive
17mGo event-driven with AWS Lambda & Event Mesh
40mEnabling event-driven automation using Knative - Robert Guske
52mServerless with Knative