We accidentally created a Serverless Application
summary
A workshop automation pipeline that spins up production IBM Cloud Kubernetes/OpenShift clusters using a GitHub issue queue, cloud functions, Code Engine and a cron scraper actually exists and works. It starts from a bash script that once took down IBM Cloud, moves through AWX, Terraform and Schematics and ends as a Flask wrapper posted to Code Engine with a Cloud Function validator. It enforces per-region VLAN limits, can launch dozens (40–60) clusters in a run, and has handled 605 automated requests saving many hours.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:26Problem with workshop infrastructure
- 3:11Evolution from bash to automation
- 7:07Terraform and its limitations
- 8:53Building the command and control system
- 10:38Tracking requests with GitHub issues
- 13:04Introducing Code Engine and serverless
- 15:53Code walkthrough and architecture
- 22:11Was it worth the journey?
- 23:13Conclusion and next steps
related talks
29mWe accidentally created a Cloud on our IBM Cloud
39mBuilding Serverless Application Pipelines
01h 18mBuilding applications with Serverless Framework ...
28mThe State of Serverless in 2020
29mUnleashing the Power of Serverless on Kubernetes with Knative, Crossplane, Dapr, KEDA, and Friends
29mGoing Serverless
30mUnleashing the Power of Serverless on K8s with Knative, Crossplane, Dapr, KEDA
29mServerless on Kubernetes: What We Learned From Customers