test: Add testing to verify consistent generation for a no change update

[engedaam]

Fixes #N/A

Description

• As part of the conversion webhooks, it is possible to apply the same resource multiple times and have the resource generation increase each time. Adding testing to make sure the resource generation does not increases for applying the same resource multiple times.

How was this change tested?

• /karpenter snapshot

Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: #
• No

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

[netlify]

✅ Deploy Preview for karpenter-docs-prod canceled.

Name	Link
🔨 Latest commit	6b1e6e3
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/66ba859986ffbc000889f454

[coveralls]

Pull Request Test Coverage Report for Build 10359984624

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 3 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.04%) to 79.281%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/providers/amifamily/ami.go	1	91.67%
pkg/fake/utils.go	2	94.56%

Totals
Change from base Build 10358539982:	-0.04%
Covered Lines:	5996
Relevant Lines:	7563

---

💛 - Coveralls

[engedaam]

/karpenter snapshot

[github-actions]

Snapshot successfully published to oci://021119463062.dkr.ecr.us-east-1.amazonaws.com/karpenter/snapshot/karpenter:0-72b86ee271a5137d9212006460ec9d3795b05a42.
To install you must login to the ECR repo with an AWS account:

aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 021119463062.dkr.ecr.us-east-1.amazonaws.com

helm upgrade --install karpenter oci://021119463062.dkr.ecr.us-east-1.amazonaws.com/karpenter/snapshot/karpenter --version "0-72b86ee271a5137d9212006460ec9d3795b05a42" --namespace "kube-system" --create-namespace \
  --set "settings.clusterName=${CLUSTER_NAME}" \
  --set "settings.interruptionQueue=${CLUSTER_NAME}" \
  --set controller.resources.requests.cpu=1 \
  --set controller.resources.requests.memory=1Gi \
  --set controller.resources.limits.cpu=1 \
  --set controller.resources.limits.memory=1Gi \
  --wait

[jonathan-innis]

Nice work! One question about ensuring that our testing covers the objects that we receive back from the apiserver too

[njtran]

Is there a way to check if the kubelet values are what we expect?