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

Default security group attached when no others declared #1124

Closed
edward2a opened this issue Aug 7, 2020 · 1 comment
Closed

Default security group attached when no others declared #1124

edward2a opened this issue Aug 7, 2020 · 1 comment

Comments

@edward2a
Copy link

edward2a commented Aug 7, 2020

Following documentation here:

This leads to believe that the SG behaviour is consistent in the sense that, if no SG's are declared when adding subnets, the same SG's will be used as the primary interface.
The actual behaviour is that ENIs created in the added subnet will have attachment to the VPC's default SG instead.
I believe this should not be the case and rather, by default, use the same SG's as the primary interface.

apiVersion: crd.k8s.amazonaws.com/v1alpha1
kind: ENIConfig
metadata: 
  name: us-west-2a
spec: 
  subnet: subnet-011b111c1f11fdf11

The code above results in ENIs with VPC's default SG.
Applying this configuration should either 'use the primary iface SGs' or 'fail to apply'.

Thank you,
Ed

@jayanthvn
Copy link
Contributor

Hi @edward2a

This is handled in #1259. Hence closing this issue.

Thank you!

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

No branches or pull requests

3 participants