Eksctl: Allow more granular control over volume configuration on NodeGroup

[tomhuang12]

Why do you want this feature?
In my use case, I would like to attach a second encrypted EBS volume to the nodes due to security requirements. The second volume is coming from a snapshot of the AMI I am using for the nodes.

What feature/behavior/change do you want?
An example cluster configuration yaml would look something like this:

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: cluster-1
  region: eu-west-1

nodeGroups:
  - name: ng1
    instanceType: m5.xlarge
    desiredCapacity: 1
    volumeMappings:
    - deviceName: "/dev/xvda"
      volumeSize: 100
      volumeType: gp2
      volumeEncrypted: true
      snapshotId: snap-0e1d1928ad4d81a
      volumeKmsKeyID: 36c0b54e-64ed-4f2d-a1c7-96558764311e
    - deviceName: "/dev/sdb"
      volumeSize: 100
      volumeType: gp2
      volumeEncrypted: true
      snapshotId: snap-012d1928ad4abc1
      volumeKmsKeyID: 36c0b54e-64ed-4f2d-a1c7-96558764311e

[darth-kermit]

Please implement this. I have been unable to use EKSCtl for this very reason. Cloudformation allows you to configure/add a second volume so it shouldn't be a problem for EKSCtl.

[sayboras]

I feel it's making sense to have this. I can spend sometime this week on this if maintainers are ok with this feature. @martina-if @cPu1

[scottbisker]

+1 for having this ability. It will greatly simplify deployments for thing like EdgeFS where a separate volume can be dedicated for the service.

[github-actions[bot]]

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.