Workshop on Defining a Reference Model for Cloud-Native Application Delivery
Talkat KubeCon + CloudNativeCon North America 2019 · on Thursday, 2019-11-21· at 10:55· Room 7AB - San Diego Convention Center, Upper Level·
summary
Proposal of a layered reference model that pins down what “application” means (metadata + resource graph) and where projects actually sit: application descriptor vs application model, Helm vs Kustomize vs DSL for configuration, packaging via OCI/Helm/OCI registry/CNAB and delivery via Spinnaker/Flagger/GitOps. It maps deployment concerns separately: rollout strategies (canary/blue‑green), platform translation into cluster primitives, and pod‑level instance controllers/operators. Gaps called out include SLI/SLO health modeling and air‑gapped packaging/versioning challenges; the output is a tooling landscape and taxonomy, not a single product.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:02The App Mgmt & Delivery Ecosystem
- 2:21Take a closer look ...
- 3:27Take a closer closer look ...
- 8:54Eg. AWS Serverless App Model (SAM)
- 11:10Application Definition & Packaging
- 14:05Checkpoint
- 15:44Application Deploy & Rollout
- 17:29App Delivery Workflow and Actions
- 22:25Workload Instance Automation & Operation
- 23:21What's the difference between Topic 28 32
- 24:16Why decouple Topic 2 & 3?
- 25:18Summary: the model multi-cloud?
related talks
24mA Decentralized Reference Architecture for Cloud-native Applications
24mReference Architecture for a Cloud Native Digital Enterprise
30mApp Delivery in Cloud Native: Where are We? What's Next?
34mManaging Distributed Cloud Native Applications Made Easy - Nikolay Valchev, SAP
43m(Mis)Understanding Cloud-Native
19mOpen Application Model: Application-centric DevOps Approach
03mGoing (cloud) Native
25mStandardizing Cloud Native Application Delivery Across Different Clouds