1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
Hello,
This is actually an expected behavior for CodePipeline, since whenever a Pipeline is executed, by nature this means there are some changes being pushed to the Source and a deployment needs to be done, so the ECS tasks will be replaced by the deployment. See the current available option here. As a solution, you might consider to split the Pipeline to multiple Pipelines for each ECS service. Alternatively, if you still would like to use the same Pipeline to deploy multiple ECS services, to ensure availability, I would recommend to increase the desired count
and minimumHealthyPercent
and maximumPercent
to maintain tasks availability during rolling update.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace un año