We need to scale up pods with warm-up by canary deployment, but it doesn't

[JehPark]

Summary

We are using the canary deployment strategy of Argo Rollouts. Our issue arises when we want to scale up the pods while using the canary deployment strategy. When we scale up the pods and deploy with a new image, the rollouts of the existing image also generate the same number of pods. In this scenario, the new image's pods follow the canary deployment strategy, allowing them to properly warm up before handling service traffic. However, the newly created pods with the existing image start handling service traffic immediately. Is there a way to prevent pod scaling for the existing image, or alternatively, to ensure that the newly created pods with the existing image also follow the canary deployment strategy?

Use Cases

We use argo-rollouts with canary deployment. Sometimes, our services need to horizontal pod scaling-up.

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.