sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

Argo CD health check for karpenter.sh/NodeClaim

Introduced 2026-08-04 · score 0.92

HOW TO USE IT

When reviewing a Karpenter v1 `karpenter.sh/NodeClaim` in Argo CD, use the bundled v3.5.0 health check: it reports Progressing while status is absent or Launched, Registered, or Initialized is reached; Healthy for `Ready=True`, Degraded for `Ready=False`, and Suspended for `Disrupting=True`.

kubectl get nodeclaims.karpenter.sh <nodeclaim-name> -o yaml

WHY THIS HELPS

Review the health of a Karpenter v1 NodeClaim in an Argo CD application.

BEFORE THIS CHANGE

NodeClaim had no bundled Argo CD health check; the release note says NodePool and EC2NodeClass had checks, but NodeClaim was missing one.

REQUIREMENTS AND LIMITATIONS

  • Version: v3.5.0
  • <nodeclaim-name> (required): Name of the NodeClaim to fetch.
  • -o yaml: Output the resource as YAML; the health script evaluates the manifest's status and conditions.
  • Prerequisite: Argo CD v3.5.0 includes the bundled health check at `resource_customizations/karpenter.sh/NodeClaim/health.lua`.
  • Prerequisite: The resource must be a Karpenter v1 `karpenter.sh/NodeClaim`.
  • Applies to Karpenter v1.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card