🚀Uber's ServiceScale Controller Enables Multi-Orchestrator Kubernetes Management
Uber's new controller lets multiple orchestrators manage the same Kubernetes workloads
TL;DR
Uber's ServiceScale controller allows multiple orchestrators to safely manage the same Kubernetes workloads, enhancing failover and scaling capabilities. It supports native Kubernetes Deployments and OpenKruise CloneSets, and was rolled out without customer-impacting outages.
Uber has published a detailed account of its new ServiceScale controller, which allows multiple orchestrators to safely manage the same Kubernetes workloads. This is a big deal for anyone running distributed systems with regional failover needs, as it simplifies scaling and failover processes. Uber's Container Platform team manages over 100 compute clusters across data centers and cloud providers, and the ServiceScale controller supports native Kubernetes Deployments and OpenKruise CloneSets. The rollout took a year and completed without customer-impacting outages.
Key Points
Uber's Container Platform team manages over 100 compute clusters across data centers and cloud providers.
The ServiceScale controller supports native Kubernetes Deployments and OpenKruise CloneSets.
Rollout of the new controller took a year and completed without customer-impacting outages.
Kubernetes v1.36 introduced staleness mitigation for controllers using a comparable approach.
CNCF recently graduated Karmada, a multi-cluster orchestration project addressing failover across clusters.
Why It Matters
If you're running distributed systems with regional failover needs, Uber's ServiceScale controller simplifies scaling and failover processes. It supports native Kubernetes Deployments and OpenKruise CloneSets, and was rolled out without customer-impacting outages. This makes it easier to inspect and manage Kubernetes objects during failover scenarios.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,567 builders reading daily.