Errors after v0.37.0 upgrade: "conditions[1].reason in body should be at least 1 chars long"

[project-administrator]

Description

Observed Behavior: Karpenter shows errors in the logs:

{"level":"ERROR","time":"2024-06-27T11:32:14.527Z","logger":"controller","message":"Reconciler error","commit":"490ef94","controller":"nodeclaim.disruption","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"trusted-nvqdc"},"namespace":"","name":"trusted-nvqdc","reconcileID":"7cd8d5d2-1d10-4806-8866-92c138032406","error":"NodeClaim.karpenter.sh \"trusted-nvqdc\" is invalid: [conditions[1].reason: Invalid value: \"\": conditions[1].reason in body should be at least 1 chars long, conditions[2].reason: Invalid value: \"\": conditions[2].reason in body should be at least 1 chars long, conditions[4].reason: Invalid value: \"\": conditions[4].reason in body should be at least 1 chars long]"}

Expected Behavior: No errors in the logs

Reproduction Steps (Please include YAML): I updated the CRDs according to the instructions by running kubectl apply manually. After that, I upgraded the helm chart from version v0.36.2 to v0.37.0. It is also worth noting, that before the chart was upgraded the existing v0.36.2 pods had been restarted (due to unrelated events).

Versions:

• Chart Version: v0.37.0

• Kubernetes Version (kubectl version): v1.29.4-eks-036c24b

• 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

[jonathan-innis]

Looks quite similar to #6326. I believe this is the same issue and gets resolved by upgrading the CRDs to the latest version as described here: https://karpenter.sh/docs/upgrading/upgrade-guide/#crd-upgrades