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

Updating Security Group of the EC2 instance doesn't update Security Group of Network Interfaces created by EKS controller #964

Closed
anhdat opened this issue May 8, 2020 · 2 comments
Assignees

Comments

@anhdat
Copy link

anhdat commented May 8, 2020

Steps to reproduce:

  • Create new ASG with SG sg-1.
  • Create a new SG sg-2.
  • Attach SG sg-2 to EC2 instances.
  • Detach SG sg-1 from EC2 instances.

Results:

  • Primary Network Interface eni-1's SG is updated to sg-2.
  • Network Interfaces created by EKS controller are still using sg-1.

Expectations:

  • All Network Interfaces attached to the node should be updated Security Group to sg-2.
@mogren
Copy link
Contributor

mogren commented May 8, 2020

@anhdat Yes, you are right that they are currently not being updated. We are working on a fix for that in #903

@mogren
Copy link
Contributor

mogren commented Sep 4, 2020

A release candidate including a fix for this is available v1.7.2-rc1

@mogren mogren closed this as completed Sep 4, 2020
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