Allow configuring multiple node groups as part of the cluster component

[bob-bins]

Almost any cluster that runs real workloads will have more than one node group, at which point there's no benefit to using the default node group option because we would have already written our own abstractions for creating node groups. I think this module should expose a param that allows adding multiple node groups instead of just one. Something like:

managedNodeGroups: Record<string, inputs.ClusterNodeGroupOptionsArgs> or Array<inputs.ClusterNodeGroupOptionsArgs>

[flostadler]

Hey @bob-bins, the default node group is mostly geared towards folks starting out with EKS or experimenting and just needing any arbitrary node group.
You're absolutely right that production use cases definitely need more diverse sets of node groups.
Right now you can disable the default node group by setting skipDefaultNodeGroup to true. That way you have full control over which manage/self-managed node groups you create.

I like the idea of adding inputs to the cluster for setting up node groups more easily! I'll track this as a feature request. In case folks are interested in this, please upvote it.