Michael Nascimento Santos
Michael Nascimento Santos
/remove-lifecycle stale
/remove-lifecycle stale
/remove-lifecycle stale
/remove-lifecycle stale
Downgrading to 1.82.4 in our case does not make the issue go away, indicating that, even if it was related to the agent, the digest information is now somehow cached...
AWS has confirmed this is definitely caused by them and they think this is a good feature, as the links (made available yesterday) show https://aws.amazon.com/about-aws/whats-new/2024/07/amazon-ecs-software-version-consistency-containerized-applications/ https://aws.amazon.com/blogs/containers/announcing-software-version-consistency-for-amazon-ecs-services/ https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html#deployment-container-image-stability There's no way...
@amogh09 , I can't see how this would address the blue-green scenario. Could you explain it, please?
@amogh09 , sure. Our blue-green deployments work by deploying a new image to the ECR repo tagged with latest and then launching a new EC2 instance (from the ECS-optimized image,...
@amogh09 in summary: the software version "inconsistency" is what makes blue green a breeze with ECS. Should we want consistency, we'd use a digest or a version tag.
@amogh09 , I think we're talking about different things. Until the ECS change, launching properly a new ECS instance properly configured for a ECS daemon service whose taskdef is tagged...