Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Only consider public subnets #1064

Merged
merged 1 commit into from
Dec 15, 2020
Merged

Only consider public subnets #1064

merged 1 commit into from
Dec 15, 2020

Conversation

ndeloof
Copy link
Collaborator

@ndeloof ndeloof commented Dec 15, 2020

What I did
Add ability to detect "public subnets" and only consider those when building the stack's network configuration.

Note: private subnets (i.e. not associated with an Internet Gateway) don't make sense for Docker ECS integration as service would not be able to pull sidecar images from DockerHub.

Related issue
#921

/test-ecs

(not mandatory) A picture of a cute animal, if possible in relation with what you did
image

@github-actions github-actions bot added the ecs label Dec 15, 2020
Signed-off-by: Nicolas De Loof <[email protected]>
Copy link
Contributor

@aiordache aiordache left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@dalegaspi
Copy link

i suppose this is not addressed as of v20.10.5 because it's still referencing the private subnets in the resulting CF template. :-(

as of right now i'm just doing a docker compose convert then comment out the private subnets.

@komatom
Copy link

komatom commented Nov 28, 2021

in which version of docker cli is this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A load balancer cannot be attached to multiple subnets in the same AvailabilityZone
4 participants