Can you do a new release with node groups?

[davisford]

I have issues

We are trying to use the cluster auto-scaler with EKS. EKS requires node groups to work properly with auto scaler. I see you've added support for node groups on Dec. 4. Is it possible to create a new release? We are having trouble trying to pull the module down by git hash, but perhaps I am missing something.

[max-rocket-internet]

EKS requires node groups to work properly with auto scaler

No it doesn't. Or you mean a different autoscaler? Like not the cluster-autoscaler?

Is it possible to create a new release?

I'm keen to do this but there's a few issues that I think we should resolve first:

#623
#627

@davisford perhaps you could test that PR?

[davisford]

Yes, I mean the cluster auto-scaler

What I meant is:

If you are running a stateful application across multiple Availability Zones that is backed by Amazon EBS volumes and using the Kubernetes Cluster Autoscaler, you should configure multiple node groups, each scoped to a single Availability Zone. In addition, you should enable the --balance-similar-node-groups feature. Otherwise, you can create a single node group that spans multiple Availability Zones.

Will see if I can test out the PRs -- I assume you mean by actually deploying. I can run TF plan and check the output, but I'm assuming your tests catch that stuff.

[max-rocket-internet]

backed by Amazon EBS volumes and using the Kubernetes Cluster Autoscaler

In this case you create an ASG per AZ. But if you are not using EBS volumes then it doesn't matter.

Will see if I can test out the PRs -- I assume you mean by actually deploying. I can run TF plan and check the output

Great! I am not using managed node groups so can't really test properly.

[davisford]

Yes, I am using EBS volumes heavily so node groups are important for us.

[iterion]

It doesn't seem like there is anything to be done for #623 - if there is I'm happy to try to tackle it to unblock a release.

[max-rocket-internet]

@iterion sure but base it off this PR that will be merged very soon: #650

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.