VPC CNI shouldn't reserve a ENI for trunk ENI if the instance doesn't support ENI trunking

[haouc]

What would you like to be added:
Currently, VPC CNI always reserve a ENI slot for trunk ENI if the Security Group for Pods feature is enabled through its ENV ENABLE_POD_ENI. If the instance type doesn't support ENI trunking, reserving a slot in those nodes doesn't sound a correct behavior and also cause inefficient usage of ENI resources thus lower IP density. VPC CNI should be knowing not to reserve a ENI for trunk ENI if the instance type doesn't support ENI trunking.

Why is this needed:
Reserving a ENI for trunk when the instance doesn't even support ENI trunking is lowering IP density and thus pod density.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

[innovativelife]

This issue was raised on behalf of TechnologyOne by our AWS Enterprise Support Lead, Allen Lu. We still consider this feature to be important, as not having this feature wastes resources.

[ali-parsfar]

Cloud we have an update on this feature request ?