03/03/2023, 10:10 AM
hi - We have an application running on kubernetes(EKS), we use rolling update strategy for our deployment. Our application does data migration from on pre m to cloud and this sometimes takes a day or two depending on the data size. The issue for us is when we do the deployment , the pod thats performing the migration gets terminated as expected . But we would want to avoid this as the migration has to be started all over again by the customer. So does anyone know of a way to exclude the pod from upgrade thats is performing the migration until the process is complete.