This is a lot of things

CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog
+
+## 04/08/2021
+
+### Branch: `patch-rgs`
+
+* Remove the resource group definitions throughout modules and submodules and use separate resource group module to pass into new variables.
+* Change `subnet_id` from `string` to `list(string)` to support `vnet` with multiple subnets.
+* Add variable `location` to use location of the resource_group dependency
+* Add variable `resource_group_id` 
+
+```hcl
+resource "azurerm_lb_backend_address_pool" "bepool" {
+  name            = "${var.name}-lbe-be-pool"
+  loadbalancer_id = azurerm_lb.this.id
+  resource_group_name = var.resource_group_name
+  # Deprecated in future azurerm releases, ignore linting
+  //  resource_group_name = ""
+}
+```
+In the `azurem_lb_backend_address_pool` resource, resource_group_name is required, so it was added back in.
+
+* `upgrade_mode = "Manual"` (line 138 in `main.tf`) since `Automatic` was throwing errors about missing parameters not set.
+

README.md

@@ -8,3 +8,11 @@ This repository is inteded to clearly demonstrate one method of deploying `rke2`
 
 We highly recommend you use the modules in this repository as stepping stones in solutions that meet the needs of your workflow and organization.  If you have suggestions or areas of improvements, we would [love to hear them](https://slack.rancher.io/)!
 
+
+__WARNING:__ The leader election process is busted.  To get this module to work you must select 1 server and rerun `01_rke.sh` in `/var/lib/cloud/instances/$INSTANCE/scripts/01_rke2.sh` on subsequent server nodes to get them to join the cluster.
+
+The `agents` module, however works just fine in joining the cluster once a master is present.
+
+## TODO:
+
+* Figure out missing inputs to get `upgrade_mode = "Automatic"` working.