Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodes of a NodeGroup with AMI type BOTTLEROCKET_x86_64_NVIDIA are not joining the cluster #7897

Open
cPu1 opened this issue Jul 25, 2024 · 1 comment
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@cPu1
Copy link
Collaborator

cPu1 commented Jul 25, 2024

The customer used eksctl to create a managed node group with the gpus set to 0 in the instance selector and specified the AMI family as Bottlerocket. Under these settings, a normal Bottlerocket AMI was expected to be configured, but the customer's managed node group was configured with an NVIDIA Bottlerocket variant, causing instances to fail to load kernel modules.

Nodegroup config:

    name: worker-1c-spot-2-v5
    availabilityZones: ["eu-central-1c"]
    spot: true
    minSize: 0
    desiredCapacity: 1
    maxSize: 60
    privateNetworking: true
    amiFamily: Bottlerocket
    taints:
      - key: nodegroup
        value: worker
        effect: NoSchedule
    propagateASGTags: true
    instanceSelector:
      vCPUs: 8
      memory: 16GiB
      cpuArchitecture: x86_64
      gpus: 0
@cPu1 cPu1 added the kind/bug label Jul 25, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Aug 25, 2024
@TiberiuGC TiberiuGC added priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases and removed stale labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

No branches or pull requests

2 participants