I’m exploring the integration of Istio for Canary deployment capabilities alongside my existing Helm-based deployment approach.

Previously, I utilized Helm as a straightforward template for managing all Kubernetes resources. With Istio, I recognize the shift towards using VirtualService and Gateway instead of traditional Ingress. However, I’m keen on retaining Helm for managing deployment templates.

In this setup, I want to have two sets of deployment and service template files. Specifically, I’d like the second deployment and service to be deployed when a particular value is provided in my custom values file (e.g., deployment: v2).

Additionally, once the Canary deployment is successfully completed, and the new version is receiving 100% of the traffic, I intend to automatically remove the old version. Is this configuration feasible?

I’ve also come across Argo Rollouts as an alternative solution, would it be suitable for my requirements?