Skip to content

Releases: terraform-ibm-modules/terraform-ibm-base-ocp-vpc

v3.3.3

06 Jun 16:19
v3.3.3
d47b01e

Choose a tag to compare

3.3.3 (2023-06-06)

Bug Fixes

  • increase the ibm_container_addons creation timeout to 1 hour(#168) (d47b01e)

v3.3.2

23 May 10:21
v3.3.2
5373f7d

Choose a tag to compare

3.3.2 (2023-05-23)

Bug Fixes

  • only deploy addons after workers are up (#163) (5373f7d)

v3.3.1

17 May 08:24
v3.3.1
1e53d36

Choose a tag to compare

3.3.1 (2023-05-17)

Bug Fixes

  • fix bug where required providers time and kubernetes were incorrectly locked to exact version instead of a range (#164) (1e53d36)

v3.3.0

08 May 13:51
v3.3.0
29bd97c

Choose a tag to compare

3.3.0 (2023-05-08)

Features

  • enable autoscaling on a given cluster (#138) (b10dd9f)
  • use the terraform-ibm-cos module to provision COS instance (#139) (ec13c1c)

v3.2.0

03 May 07:50
v3.2.0
a9c06c2

Choose a tag to compare

3.2.0 (2023-05-03)

Features

  • option to pass list of subnets or subnet prefix (#142) (a9c06c2)

v3.1.1

02 May 18:57
v3.1.1
5019315

Choose a tag to compare

3.1.1 (2023-05-02)

Bug Fixes

  • scope the ibm_container_cluster_versions data lookup by region to enhance performance and ensure consistent results (#160) (5019315)

v3.1.0

26 Apr 15:50
v3.1.0
d78d671

Choose a tag to compare

3.1.0 (2023-04-26)

Features

v3.0.1

30 Mar 09:02
5f11656

Choose a tag to compare

3.0.1 (2023-03-30)

Bug Fixes

  • Added example to add rules to security groups (#110) (5f11656)

v3.0.0

29 Mar 14:09
v3.0.0
c1f831e

Choose a tag to compare

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
    }
  ]

v2.3.1

24 Mar 15:06
v2.3.1
208eb88

Choose a tag to compare

2.3.1 (2023-03-24)

Bug Fixes

  • add count to the data block so that it does not execute when var.verify_worker_network_readiness is set to false (#91) (208eb88)