Skip to content

nodeclaim failing, node is created but not added to the cluster #7738

Open
@sambordoloi

Description

@sambordoloi

Description

Observed Behavior:
Conditions:
Last Transition Time: 2025-02-14T07:15:25Z
Message: object is awaiting reconciliation
Observed Generation: 1
Reason: AwaitingReconciliation
Status: Unknown
Type: Initialized
Last Transition Time: 2025-02-14T07:15:25Z
Message: Node not registered with cluster
Observed Generation: 1
Reason: NodeNotFound
Status: Unknown
Type: Registered
Last Transition Time: 2025-02-14T07:15:27Z
Message:
Observed Generation: 1
Reason: Launched
Status: True
Type: Launched
Last Transition Time: 2025-02-14T07:15:25Z
Message: Initialized=Unknown, Registered=Unknown
Observed Generation: 1
Reason: ReconcilingDependents
Status: Unknown
Type: Ready
Image ID: ami-0262a19088a11e248
Provider ID: aws:///ap-south-2b/i-0e593f835ff381a22

Expected Behavior:
it should be ready

Reproduction Steps (Please include YAML):

Versions:

  • Chart Version:
  • Kubernetes Version (kubectl version):
    1.30
  • 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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinglifecycle/staletriage/needs-informationMarks that the issue still needs more information to properly triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions