Infinite Plan Update on eks_managed_node_group for launch_template version -> $Default

[sinkr]

Infinite Plan Update on eks_managed_node_group for launch_template version -> $Default

[bryantbiggs]

that is a lot of interesting configurations - may I ask why you are approaching your configuration from this perspective? meaning:

1. Why use the node group sub-module independent of the overall EKS module?
2. Why use a custom launch template outside of the module when the module already supports a custom launch template that is "safer" for EKS?

[sinkr]

Hi Bryant, thank you for the response.

I can't definitively speak to why I ended up on this combo, however, loosely I think it had to do with not getting the correct disk_size and wanting the tagging to take place on all attached entities, like ENIs, EBS, etc.

IIRC, I feel like the only way I was able to get that combo was with this above, but perhaps some other iteration would work, however, I think long-term I'm moving towards Karpenter.

After many hours of debugging, I found that if I explicitly set launch_template_version to the current integer value, the infinite plan goes away, however, I do feel like there's an opportunity here to add logic such that we do not go to $Default unnecessarily.

My initial hypothesis was that the latest (or specified) launch template revision wasn't tagged as Default, however it was.