Philipp Strube

To make it easier to understand, I created a simple config to reproduce the issue. https://github.com/pst/debugrecreateplan The example repo shows the behaviour with both the official kubernetes provider as well...

Likely related upstream issue: https://github.com/hashicorp/terraform/issues/22572

This is definitly still an issue and it's not Kubestack specific, but generally an issue with Terraform. I hope moving away from the in-module manifests and towards the new native...

Can you provide more context? I unfortunately don't understand what you're asking for.

The nodes are created using the [`aws_eks_node_group` ressource](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_node_group). I believe the corresponding attribute for the `launch_template` used for the `aws_eks_node_group` would be this: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_template#block-devices However, that's not currently exposed yet...

@pp23 my understanding is the same as yours. The fix would be to have the provider move away from using the annotation at all. As I stated in the issue...

Thanks for reporting. Do you have a manifest and kustomization to reproduce this?

Thanks for adding more details. Unfortunately, I don't have an immediate idea what the root cause could be here. I'll leave this open to see if other people can add...

I don't use helm, the support for helm was contributed and I accepted it. But I won't be able to assist with issues around it.

Related: https://github.com/kbst/terraform-provider-kustomization/pull/89