fix(ecs): evaluate targetgroup healthcheck in instance healthcheck #6307
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
edgarulg
requested review from
jasonmcintosh,
link108,
christosarvanitis and
dbyron-sf
...rc/main/java/com/netflix/spinnaker/clouddriver/ecs/services/ContainerInformationService.java
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
But In the server group events we can see unhealthy issues.
Here is the issue in ECS AWS console.
As part of my changes I search for targetGrouphealths and then use them to set unhealthy statuses to the instance.