-
Notifications
You must be signed in to change notification settings - Fork 580
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
Set ASG subnet to only private subnets #2191
Comments
/kind bug |
Hello @sedefsavas I think this feature is pretty much required in most scenarios. I cannot think of a case were we want to have machines in public subnets. I tried using filters for subnets in the MachinePool to overcome this issue but as pointed out in the code on the initial comment, only the ID is used, filters are ignored. This is how it would look like with a filter:
|
@paurosello cluster-api-provider-aws/pkg/cloud/scope/shared.go Lines 68 to 70 in f7ef6f4
Is there another scenario this fix does not cover? |
Oh, that's nice already. We were thinking on using the filters to assign specific MachinePools to specific subnets with filters but I think it would be a completely different issue right? |
In AWSMachinePool, if subnets are not specified, we add all available subnets to the AutoScalingGroup.
Instead, the default should be only private subnets IMO.
cluster-api-provider-aws/pkg/cloud/services/autoscaling/autoscalinggroup.go
Lines 148 to 152 in da8c0c4
What do you all think?
The text was updated successfully, but these errors were encountered: