Cloud Foundry 101 for Kubernetes Users
summary
Compares concrete workflows: deploying on Kubernetes requires building a Docker image, writing manifests and wiring secrets, while Cloud Foundry reduces that to CF push + buildpack-driven staging that produces a droplet and layered app image. Explains CF internals: Diego scheduler, Gorouter routing, Loggregator logs, service binding injection, and Eirini on Kubernetes (deployable via Helm). Notes limitations: no built-in automated rollouts, tasks are single-run, and platform claims fast installs—operators report a ~30‑second bootstrap for simple CF components.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:34COMMON IDEAS (2) • YAML almost everywhere • The app is in a container • Everything is either a long-running process (LRP) or a task LRP is central: a process that is monitored and restarted if needed has health checks
- 8:50DROPLET AS INTERMEDIATE BUILD PRODUCT
- 10:13HOW KUBERNETES FEATURES MAP TO CF
- 12:20SECRET AND CONFIGURATION MANAGEMENT
- 13:39CONTAINER PLACEMENT • K8s: lots of ways to influence placement . CF: not much influence • the default scheduler Diego does it for you
- 20:07AUTOMATED ROLLOUTS AND ROLLBACKS
- 22:30TYPICAL APP DEVELOPER WORKFLOWS
- 23:46DEPLOY A NEW APP IN CF
related talks
48mKubernetes and or Cloud Foundry - State-of-the-art cloud platforms
46mWhat's Cloud Foundry and why you want to use it
38mLet's Run Cloud Foundry on Kubernetes
30mCF^3 - Using Kubernetes as the Cloud Foundry IaaS
06mHow CFCR tackles Day 1& 2 Ops for Production Kubernetes
25mPaving the Road to Eirini
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes