How to Build Your Own PaaS from the Cloud Native Landscape - Jared Watts, Upbound
summary
Shows how to assemble a full opinionated PaaS by composing cloud native projects with Crossplane: provider-gcp and provider-helm create a GKE cluster and install Prometheus, Jaeger, Fluentd, Rook and Flux from an Upbound Cloud Registry package. Developers declare a single cluster object (small/medium/large, node count, service versions) and Crossplane renders compositions, patches concrete machine types and enforces policy (OPA suggested). Demo provisions a one-node GKE cluster and a working platform; Flux then deploys Ghost, Redis and Mongo from Git via Flux continuous deploy.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:48The Cloud Native Landscape
- 3:10Visualization
- 5:21Architecture
- 6:40Platform API
- 8:06Composition Hierarchy
- 9:12Developer Configuration
- 10:56Continuous Deployments
- 11:38API Complexity
- 12:15Demo
- 13:27Command Prompt
- 17:37Adding Deployment Key
- 18:56Connecting to Workload Cluster
- 20:06Conclusions
related talks
37mPlatformOps with Crossplane
34mDoing GitOps for multi-cloud using Crossplane & Flux2
35mBuilding and Enabling APIs with Crossplane 1
35mPlays Well with Others: Composability for Cloud Native Applications
36mHow to Build Cloud-Native Platforms with Kubernetes
48mDoing multi-provider Kubernetes in GitOps mode with CrossPlane
33mEliminating the Gap Between Development and Production with Kuber...
36mCrossplane Intro And Deep Dive - The Cloud Native Control Plane Framework