-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Inserting New Mappings into node_groups leads to ddestructive behavior #2808
Comments
Thanks for opening the issue, @kenafoster. The name of the issue is a bit misleading, though. What leads to the destruction and recreation of resources is not the inclusion of new nodes to the mapping but the rearranging of the order. This is a curious finding that I think I might've stumbled across before as well. Indeed, it is due to us using the nebari/src/_nebari/stages/infrastructure/template/aws/modules/kubernetes/main.tf Lines 71 to 74 in e26e605
Hence, each new node_group created by terraform is then referenced by its resources name e.g.
However, as mentioned above, once you included more nodes and re-arranged the order, this lead to the following correspondence:
The problem is that the already created resource As you might have considered, the best approach would be to use the |
Discussed in the meeting today, we are open to fixing this by having terraform reference things by node group name rather than list position and we think that is a better way to handle this, but no one is assigned at the moment. @kenafoster Do you have interest in working on this? |
Describe the bug
Modify a Nebari AWS deployment node group definition like so:
Nebari destroyed and recreated the third item in the mapping (so grp_3 became grp_4) then created a new fourth and fifth item
Expected behavior
Create new grp_4 and grp_5 while leaving grp_3 unchanged
OS and architecture in which you are running Nebari
MacOS / ARM Apple Silicon
How to Reproduce the problem?
Make a change in a nebari-config such as:
Command output
The text was updated successfully, but these errors were encountered: