v3.0.0

3.0.0 (2023-03-29)

Refactoring

• This change updates some of the examples (under the 'examples' folder) to create worker pools spread across availability zones, as opposed to multiple single zone worker pool. This capability always existed in the root module, but was not demonstrated specifically by the examples. The actual logic in the root module to create the worker pools has not changed.

BREAKING CHANGES

• The defaults in the worker_pools input variable have been removed, as they were making assumptions on the value passed to the vpc_subnets input variable. The naming in the worker_pools defaults were also giving the false impression that the worker pools were defined by availability zone. worker_pools is now a mandatory input. If you relied on the defaults in version 2.X.X of the module, simply set the value worker_pools to the following when moving up to version 3.0.0

[
    {
      subnet_prefix    = "zone-1"
      pool_name        = "default"
      machine_type     = "bx2.4x16"
      workers_per_zone = 2
    },
    {
      subnet_prefix    = "zone-2"
      pool_name        = "zone-2"
      machine_type     = "bx2.4x16"
      workers_per_zone = 2
    },
    {
      subnet_prefix    = "zone-3"
      pool_name        = "zone-3"
      machine_type     = "bx2.4x16"
      workers_per_zone = 2
    }
  ]