ENI tagging

[cdenneen]

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.

[errordeveloper]

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.
The first two ENIs appear like primary ENIs of the nodes that are not used by the network drive, that's why they only have primary IPs and and different description format. The driver uses non-primary ENIs, it creates those and allocates IPs as needed for scheduling pods, but doesn't automatically garbage collect when pods go away.

[errordeveloper]

@christopherhein @tiffanyfay do you think we should open an issue elsewhere? Any other thoughts on this?

[whereisaaron]

Despite tags for EIP being added to AWS API back in 2017, AWS CloudFormation is yet to support them 😭

[whereisaaron]

We can track our wait for CF EIP support here:
aws-cloudformation/cloudformation-coverage-roadmap#84

[josegonzalez]

Seems this was added in November to CF :)

[michaelbeaumont]

ENIs aren't tagged it seems

[github-actions]

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.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.