Feature: Add FleetID for every EC2 CreateFleet call for debugging purposes in LOG_LEVEL="debug"

[youwalther65]

Description

What problem are you trying to solve?
Currently Karpenter logs FleetID for EC2 CreateFleet calls only in case of InsufficientInstanceCapacity errors already here.

For debugging purposes, i.e. LOG_LEVEL="debug", adding the FleetID for every EC2 CreateFleet call would be helpful. Using FleetID one can lookup all the details of EC2 CreateFleet call in AWS CloudTrail.

How important is this feature to you?

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[DerekFrank]

Discussed this with the team, we've shy-ed away from introducing to much logging that happens on the happy path into DEBUG. Because cloudtrail logs already should have all of these requests, I think this is an argument either to introduce tracing or a TRACE level.