Removing Fargate Detecting Condition #92
Open
hochizo5940 wants to merge 1 commit into
Open
Conversation
Contributor
|
I would be willing to take over maintainership from @teralytics and merge the patches / PRs submitted by users. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In 2022, AWS announced the new feature ECS Service Connect which helps to create service mesh feature easily.
The service connect container is not described on Task definition, but described on tasks.
Since Name checking between task's container and task definition's container is not applied when ecs runs on a fargate, there is a case that target is created for ecs service connect container.
This problem solved with this commit.