BYO Infrastructure: Who needs to run a control plane, anyway?
summary
Argues that the control plane can run in public clouds while on‑prem keeps compute and storage, using Kubernetes everywhere and manage updates in a public cloud so teams only own the data plane. Describes using a service mesh like Istio over a VPC to enforce corporate routing and security and service mesh overlaying a VPC for multi‑cluster segmentation. Proposes CRDs to standardize serverless across providers and a neural prediction layer that prewarms containers, ties attestation to TPMs for trust, and uses tools like Lens and registries.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:06Writing Applications on Bare Metal
- 5:11Microservices Architecture
- 7:25Event-Driven Architecture for a Cloud-Native Environment
- 10:13Single Responsibility Principle
- 10:48Are Microservices the Way To Go for Everything
related talks
06mLightning Talk: Unifying Hybrid Clouds: A Journey Through Multi-Control...
06mKubernetes as the Control Plane for the Hybrid Cloud
22mMaking the case for a vendor-neutral control plane to scale AI in enterprise settings.
36mKubernetes as the Universal Control Plane: From Pods to Multi-Cloud Infrastructure
36mPanel: Control Plane vs Data Plane: Untangling the Tenets of Multitenancy
40mKubernetes is Your Cloud Control Plane
26mKeynote: Kubernetes - The Universal Control Plane
40mMay the Control Plane be with you: Kamaji and the rise of Kubernetes at scale