-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Additional node security group rule for metrics-server #2389
Comments
I believe we already cover the 2nd rule, but please feel free to open a PR for the first rule to be added to the recommended security group rules |
You cover just the first one - https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/node_groups.tf#L119 |
ah, overlooked that one. We cover the first one in terraform-aws-eks/node_groups.tf Lines 110 to 117 in 0e3cb9a
|
Agreed, looks like you added that in release 19.0, excellent. I will go ahead and remove it from our own module. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.
Is your request related to a problem? Please describe.
No
Describe the solution you'd like.
So far we used two additional SG rules for our nodes to enable metrics-server communication:
Looks like the first one was included implicitly with #2353 so we commented it out in our module's IaC.
As per metrics-server documentation the second one is also needed - https://github.com/kubernetes-sigs/metrics-server#requirements
I am more than happy to open a PR for this.
Describe alternatives you've considered.
I can continue to have the SG rule added with our IaC.
Additional context
N/A
The text was updated successfully, but these errors were encountered: