Unity in Diversity: Architecting “Shared-Fir...
summary
Motorola Solutions runs 50–60 production clusters (AKS/EKS/GKE/OpenShift) hosting 50–60 products and 2,000–4,000 microservices per cluster and achieves 50–70% infrastructure savings by using a custom Kubernetes Admission Controller to inject tolerations and enforce namespace-to-nodepool placement, per-tenant NGINX ingress controllers (mapped to dedicated cloud NLBs) to limit blast radius, external-dns plus route53/cloud DNS for HA, cert-manager + external-secret-operator with DigiCert for automated cert lifecycle, and HPA/VPA/KEDA plus cluster-autoscaler for resource isolation and scale.
AI-written summary · about
chapters (11)
- 0:00Shared Kubernetes platforms intro
- 2:29Mission-critical workloads ops
- 5:17Correct workload deployment with node pools
- 7:03Resilient ingress layers design
- 10:32DNS conflicts and high availability
- 13:21Certificate lifecycle automation
- 18:17Multi-tenant resource scaling
- 20:23Observability security SRE FinOps
- 24:34Unifying practices across environments
- 27:41Cost optimization and business impact
- 29:06Key takeaways and closing
related talks
31munlighted, but what about Security and Multi tenancy?
36mOptimizing Resource Usage in Kubernetes
32mKubernetes Namespaces Unleashed: Unlocking the Full Potential of You...
28mOverview Of Challenges And Solutions For Orchestrating Applications To Multiple DC And Edge Clusters
32mRunning Kubernetes in a Manufacturing Line – What Could Possibly...
33mSpace Invaders for Kubernetes: Consolidating 50 Clusters at Scale
35mKubernetes journey
37mRunning Kubernetes in a Manufacturing Line