Skip to content
This repository was archived by the owner on Dec 20, 2025. It is now read-only.

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Apr 10, 2025

Deployments using ECS are marked successful by Spinnaker but the ECS service is unhealthy when target group mappings are defined in the configuration.

Here is pipeline execution with the successful deployment in Spinnaker:
Captura de pantalla 2024-11-21 a la(s) 1 30 51 p m
Captura de pantalla 2024-11-21 a la(s) 1 31 35 p m

But In the server group events we can see unhealthy issues.
Captura de pantalla 2024-11-21 a la(s) 1 31 58 p m

Here is the issue in ECS AWS console.
Captura de pantalla 2024-11-21 a la(s) 1 32 52 p m

As part of my changes I search for targetGrouphealths and then use them to set unhealthy statuses to the instance.


This is an automatic backport of pull request #6307 done by [Mergify](https://mergify.com).

…6307)

* fix(ecs): include healthcheck status from targetgroups in instance healthcheck

* test(ecs): add tests for default behavior and targetgroup healthchecks

* fix(ecs): check null for loadBalancer attribute

* refactor(ecs): improve testing and use targetHealth to determine status only if containerHealthcheck is UNKNOWN

* fix(ecs): evaluate TargetHealth check if container deployed does have target groups associated

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit 7ce44a3)
@mergify mergify bot added the auto merged Merged automatically by a bot label Apr 10, 2025
@mergify mergify bot merged commit c8c9d4c into release-1.36.x Apr 10, 2025
24 checks passed
@mergify mergify bot deleted the mergify/bp/release-1.36.x/pr-6307 branch April 10, 2025 18:48
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

auto merged Merged automatically by a bot target-release/1.36

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants