Skip to content

Commit

Permalink
docs: Update migration guide to filter NodeClaimNotFoundError
Browse files Browse the repository at this point in the history
  • Loading branch information
jigisha620 committed Aug 14, 2024
1 parent 0f98280 commit 67847d1
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions website/content/en/preview/upgrading/v1-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -407,3 +407,7 @@ This table shows v1beta1 metrics that were dropped for v1:
| NodeClaim | karpenter_nodeclaims_drifted |
| Provisioner | karpenter_provisioner_scheduling_duration_seconds |
| Interruption | karpenter_interruption_actions_performed |
{{% alert title="Note" color="warning" %}}
Karpenter now waits for the underlying instance to be completely terminated before deleting a node and orchestrates this by emitting `NodeClaimNotFoundError`. With this change we expect to see an increase in the `NodeClaimNotFoundError`. Customers can filter out this error by label in order to get accurate values for `karpenter_cloudprovider_errors_total` metric. Use this Prometheus filter expression - `({controller!="node.termination"} or {controller!="nodeclaim.termination"}) and {error!="NodeClaimNotFoundError"}`.
{{% /alert %}}

0 comments on commit 67847d1

Please sign in to comment.