Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Elastigroups [SpotInst] ignores VPCZoneIdentifier #543

Closed
mo-gr opened this issue Oct 23, 2018 · 0 comments · Fixed by #544
Closed

Support for Elastigroups [SpotInst] ignores VPCZoneIdentifier #543

mo-gr opened this issue Oct 23, 2018 · 0 comments · Fixed by #544
Assignees
Labels

Comments

@mo-gr
Copy link
Contributor

mo-gr commented Oct 23, 2018

When the Appserver has a VPCZoneIdentifier configuration, like:

VPCZoneIdentifier:
          Fn::FindInMap:
            - LoadBalancerSubnets
            - Ref: AWS::Region
            - Subnets

This should be translated to the Elastigroup create argument compute.subnetIds.

Currently, this does not happen, resulting in instances being potentially created in the wrong subnets.

A workaround is to explicitly specify the compute.subnetIds argument in the Elastigroup configuration:

Elastigroup:
  compute:
    subnetIds:
      Fn::FindInMap:
            - LoadBalancerSubnets
            - Ref: AWS::Region
            - Subnets
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants