The article explores the use of Argo Rollouts, a Kubernetes controller, for orchestrating progressive delivery workflows in applications with multiple services, addressing both modern and legacy scenarios. It discusses how Argo Rollouts, typically supporting single-service deployments, can be adapted for applications requiring simultaneous deployments of multiple microservices. The text provides a practical example of an application with a backend and frontend, explaining how progressive delivery can be achieved using different strategies like Blue-Green and Canary deployments. It emphasizes the challenges in legacy systems where microservices must maintain the same version, highlighting the complexity involved in ensuring version consistency across services during rollouts. The article contrasts this with the simplicity of modern applications, where microservices can run different versions independently, reducing deployment complexity. It ultimately suggests that the legacy pattern should be a temporary solution until applications can be refactored to allow independent deployments of microservices, aligning with the core purpose of using microservices.