-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
ENI tagging #751
Comments
Thanks for reporting this @cdenneen! Unfortunately, this is outside of our control. These ENIs are managed by the network driver. I believe that some ENIs also get created by EKS itself, but I'm not fully familiar with those, it's really an implementation detail to me and I would guess that in the future that area may evolve. |
@christopherhein @tiffanyfay do you think we should open an issue elsewhere? Any other thoughts on this? |
Despite tags for EIP being added to AWS API back in 2017, AWS CloudFormation is yet to support them 😭 |
We can track our wait for CF EIP support here: |
Seems this was added in November to CF :) |
ENIs aren't tagged it seems |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Add readiness probe so controller does not report "Ready" prematurely
Notice no tagging on any of these ENI's created.
Description for Worker Nodes isn't consistent.
Also not sure why one of the 2 nodes has 2 ENIs and the other has 1.
The text was updated successfully, but these errors were encountered: