Closed mohankumarmani closed 2 months ago
@mohankumarmani Have you tried upgrading to v0.28.1
and seeing if this solves the orphaned node issue entirely. Karpenter now has a built-in timeout to ensure that nodes register to the cluster within a static 15m timeout after launch. If this isn't fulfilled, Karpenter will auto-terminate the Machine and attempt to launch another one.
For nodes that go NotReady
after registering to the cluster, we have a separate flow that is proposed for that which is captured in aws/karpenter-core#750
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Version Karpenter Version: v0.27.0
Kubernetes Version: v1.23
we do see some nodes created by karpenter stay orphan and logs with
controller.inflightchecks Inflight check failed for node, Expected resource "memory" didn't register on the node
controller.inflightchecks Inflight check failed for node, Expected resource "ephemeral-storage" didn't register on the node
do we have any metric to check on how often we get or node details ? unless we check on cluster , we don't get to know any detailsthough it can fixed in future versions but to know if any nodes not avail for any reason which are planned to provision by karpenter, it should have a metric to know the status