feat: Add VMReserved to InstanceTypeOverhead

[jukie]

Relates:

• Discover Instance Type Capacity Memory Overhead Instead of vmMemoryOverheadPercent aws/karpenter-provider-aws#5161
• feat: Discover Instance Type Memory Capacity aws/karpenter-provider-aws#7004

Description
The underlying OS or VM hypervisor consumes additional resources that should be tracked as overhead. In the linked PR this overhead is being subtracted from the overall capacity but it may be preferable to instead add them here.

How was this change tested?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jukie
Once this PR has been reviewed and has the lgtm label, please assign ellistarn for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @jukie. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coveralls]

Pull Request Test Coverage Report for Build 10896270221

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 6 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.06%) to 80.733%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/node/termination/controller.go	2	67.6%
pkg/controllers/disruption/consolidation.go	4	87.25%

Totals
Change from base Build 10891799591:	-0.06%
Covered Lines:	8389
Relevant Lines:	10391

---

💛 - Coveralls

[jukie]

Thinking more it probably makes sense to keep this within overall capacity measurements