Quarks - New Building Blocks for Deploying on Kubernetes
summary
Quarks is a CF operator that converts BOSH manifests into k8s custom resources, splitting build-time image creation from runtime deployment so each BOSH release gets its own image and the system supports per-release images and granular updates. It runs rendered BPM jobs that capture stdout and persist results as versioned secrets, so the operator can generate and version secrets from job stdout and issue certificates, create statefulsets and services, and enable canary/blue‑green style replacements while keeping Kubernetes as the scheduler.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:17Quarks Location
- 2:44What We're, What We're Not?
- 6:30Why Are We Doing This?
- 7:21Why Kube Primitives weren't Enough?
- 8:49Building Blocks
- 12:01User Controlled Resources
- 12:20High Level Architecture
- 14:16BDPL COMPONENT
- 20:59BDPL+ESEC COMPONENT
- 24:40Next Steps
- 26:15Call To Action
related talks
18mBuilding a Kubernetes Operator in Quarkus
19mPaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native
30mFrom 0 To Production-Grade With Kubernetes Native Development
50mSecuring Serverless Functions on Kubernetes with Quarkus Extensions
46mKubernetes. From 0 to Production-Grade with Java.
01h 01mTaming Kubernetes Streamlining Inner loop Development for Distributed Systems
39mCoding Kubernetes for kids with Scratch and Che
31mKubernetes Operators within Reach of Any Developer