Adding workers deletes existing workers first

[ernestmartinez]

I deployed an AD-Spanning Cluster with 5 worker nodes. I then edited the env-vars file and changed the nodes count to 6 and executed another "Apply". It first deletes the existing 5 nodes then re-creates the 6. This is not the desired behavior, it should just add the additional node. I also tried changing the default in variables.tf with same result.

[benofben]

@smithzc what do you think is going on here?

[smithzc]

@benofben @ernestmartinez I suspect this has to do with the way we are using the index%3 to distribute nodes across each AD. Let me do some testing on this and I will see what I find. I suspect a single AD expansion will work just fine, automated cluster expansion has been on my to-do list a while now so it needs some attention.

[smithzc]

Closing this issue for now - the AD spanning template has been deprecated with the 2.0.0 release. I will be testing scale up/down with v2.0.x in the near future.