Mohit Kumar Sharma

@huikang after the abort both subsets should point to stable hash

or the pod hash label should be removed completely after abort

I just figured out that Before rollout starting and after rollout completed both canary and stable subsets should point to stable pod hash template example ``` weights: canary: podTemplateHash: 74c7887f8...

@huikang which means its wrong, bec in that case canary subset will point to the canary replicaset that does not have any pod running meaning canary requests will fail. Ideally...

even if virtual service is having weight 0 for the canary, there is a case when you have session affinity enabled then in that case your traffic will still go...

@huikang