Kubernetes 101 for Quarks and Eirini Users
summary
Quarks lets Cloud Foundry components run natively on Kubernetes while Eirini maps app start requests to Kubernetes objects so apps avoid nested containers and use the cluster scheduler. Staging executes as a Kubernetes Job with three sequential containers that download sources build the droplet and upload to the Bits service which then forms the app image and a StatefulSet runs the app. Installation uses Helm charts and chart dependencies and Helm v2 with Tiller. Debugging uses kubectl describe logs and exec and watch for storage class and secret backup pitfalls staging runs as a Kubernetes Job with three sequential containers droplets uploaded to Bits service and converted to app images install via Helm with chart dependencies and Helm v2 Tiller
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:52Why Quarks Kubernetes
- 1:36Quarks Kubernetes Components
- 6:08Quarks Magic
- 6:52Docker Images
- 7:37Components
- 8:48Secrets
- 11:08Staging Eirini
- 12:10Stateful Sets
- 13:01Informal API
- 14:07Helm
- 17:02Install Foundry
- 18:13Upgrade Foundry
- 28:25Debugging Summary
- 30:38Extensions
- 31:03Eirini Sessions
- 31:13Office Hours
- 31:34Resources
- 31:46Outro
related talks
25m"Kube" your Enthusiasm: Bringing Cloud Foundry and Kubernetes...
26mMicroservices With Cloud Foundry and Kubernetes
46mKubernetes. From 0 to Production-Grade with Java.
28mCloud Foundry 101 for Kubernetes Users
01h 01mTaming Kubernetes Streamlining Inner loop Development for Distributed Systems
06mKeynote: The Kubernetes Application Registry: Easily Deploying Complex Applications with CoreOS Quay
42mKubernetes native development workflows
49mKubernetes. From 0 to Production-Grade with Java