Deployment and Management in the Age of Cloud Integrated Applications
summary
Deploys a Kubernetes-based Twitter sentiment app that wires pods to a cloud message queue, a managed sentiment API, a managed database and a visualizer, and shows those pieces actually provisioned and torn down. Demos use Terraform workspaces (separate TF state per instance) to create resource groups, Kubernetes Service Catalog bindings to provision Azure services and export connection strings into Kubernetes secrets, Helm to install/delete instances, and CNAB/Porter as a flexible packaging option. Secret handling and per-instance lifecycle management are the core problems demonstrated and resolved end-to-end.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:17Agenda
- 1:47Deployment
- 3:27Rethinking the application
- 7:00Cloud Distributed Applications
- 12:07Terraform State/Workspaces
- 13:33Terraform: Impressions
- 19:11Open Service Broker
- 19:54Kubernetes Service Catalog
- 20:49How do these components line up
- 21:55API Diagram
- 24:18SVCAT: Impressions
- 31:32Cloud Native Application Bundles (CNAB)
- 33:02Bundle components
- 33:46CNAB Implementations
- 34:54CNAB: Impressions
related talks
30mImproving the Cloud Development Experience: The Good, The Bad...
34mBoarding Completed and Liftoff to the Cloud
48mSelf-serve app infrastructure using Azure Deployment Environments
33mEliminating the Gap Between Development and Production with Kuber...
41mRediscovering DevOps' Heartbeat: A Journey with Cloud Development Environments
47mGoing from containers, to pods, to Kubernetes – help for developer environments!
26mStreamline Your App Development With the Power of Cloud Native Tools
05mKeynote: Manage the App on Kubernetes
