Are your platform teams constantly saying "no" to requests for new Kubernetes clusters? The traditional approach to Kubernetes multi-tenancy forces organizations to choose between cluster sprawl or restrictive namespaces - neither of which fully meets the needs of modern development teams.
Lukas Gentele, CEO and co-founder of Loft Labs, shares how vCluster is transforming the way organizations handle multi-tenancy in Kubernetes. By running virtual Kubernetes control planes inside namespaces, vCluster enables teams to experiment with different versions, operators, and configurations while maintaining efficient resource usage.
Key topics covered:
How vCluster solves the limitations of namespace-based multi-tenancy
Running multiple Kubernetes versions in the same cluster for testing and gradual upgrades
Managing bare metal GPU resources efficiently for AI/ML workloads
Balancing standardization with developer autonomy in platform engineering
Using virtual clusters for cost-effective testing across multiple Kubernetes versions
Whether you're a platform engineer looking to say "yes" more often or a development team seeking greater autonomy within Kubernetes, this discussion offers practical insights into modern multi-tenancy approaches.
Podden och tillhörande omslagsbild på den här sidan tillhör
Cory O’Daniel, CEO of Massdriver. Innehållet i podden är skapat av Cory O’Daniel, CEO of Massdriver och inte av,
eller tillsammans med, Poddtoppen.