Going the Kubernetes Way: Self-hosted or a Managed Solution
summary
Compares running Kubernetes in-house versus a managed service with concrete tradeoffs: self-hosted gives full control and high configurability and suits enterprises, legacy on‑prem apps or strict compliance; costs include quarters of training, hiring and ongoing maintenance plus tricky production troubleshooting. Managed solutions (EKS/GKE/AKS/VKE/DOKS) hand off upgrades, support and ops so startups avoid ops hires; provider-specific claims include free control plane at Vultr, GPU (NVIDIA) support, Crossplane integration coming and a 250 credit bonus for signups.
AI-written summary · about
chapters (10)
- 0:00Kubernetes hosting dilemma
- 3:52Relevance of topic
- 6:22Agenda
- 8:11Self-hosted benefits
- 10:37Choosing self-hosted
- 13:54Self-hosted challenges
- 16:48Managed services reasons
- 18:36Managed providers
- 20:44Vulture Cloud offer
- 21:26Conclusion
related talks
34mSelf-Hosted Kubernetes: How and Why [I]
24mWhy Use Managed Kubernetes?: It's Dangerous to Go Alone!
21mDeploying Kubernetes at scale
32mLaying the Foundation: Real World Kubernetes Deployment Patterns
08mKeynote: Fair Share - What Shared Responsibility Means for Managed Kubernetes Cluste...
36mManaging und Running Multiple Kubernetes Clusters
49mThe state of on-prem Kubernetes
33mManaged Kubernetes Service: Day Zero Survival Pack