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

[Feature] add nodeadm merge functionality for AL2023 MNG #8043

Open
youwalther65 opened this issue Nov 25, 2024 · 0 comments
Open

[Feature] add nodeadm merge functionality for AL2023 MNG #8043

youwalther65 opened this issue Nov 25, 2024 · 0 comments
Labels
kind/feature New feature or request priority/important-soon Ideally to be resolved in time for the next release

Comments

@youwalther65
Copy link

What feature/behavior/change do you want?

I want to be able to create an AL2023 managed node group (MNG) with custom nodeadm data like

managedNodeGroups:
...
- name: mng-custom-AL2023
  minSize: 1
  maxSize: 2
  desiredCapacity: 2
  instanceTypes: [ "m6gd.large", "m7gd.large" ]
  amiFamily: AmazonLinux2023
  ami: ami-xxx
  overrideBootstrapCommand: |
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="BOUNDARY"

    --BOUNDARY
    Content-Type: application/node.eks.aws

    ---
    apiVersion: node.eks.aws/v1alpha1
    kind: NodeConfig
    spec:
      instance:
        localStorage:
          strategy: RAID0

    --BOUNDARY
  updateConfig:
    maxUnavailable: 1

Currently I am getting an error stating:

$ eksctl create nodegroup -f eksctl-NVME-AL2023.yaml
Error: could not create cluster provider from options: managedNodeGroups[1].overrideBootstrapCommand is not supported when using a custom AMI based on AmazonLinux2023 (managedNodeGroups[1].ami)

I have expected, that eksctl would merge the custom nodeadm data with the ones it creates per default (cluster specification).

Why do you want this feature?

Using advanced nodeadm features allow customization of for example node local storage to move kubelet and containerd related stuff to NVME based devices for segregation and enhanced performance.

@youwalther65 youwalther65 added the kind/feature New feature or request label Nov 25, 2024
@TiberiuGC TiberiuGC added the priority/important-soon Ideally to be resolved in time for the next release label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/important-soon Ideally to be resolved in time for the next release
Projects
None yet
Development

No branches or pull requests

2 participants