Skip to content

Releases: terraform-ibm-modules/terraform-ibm-landing-zone

v6.0.1

26 Sep 08:20
v6.0.1
6e70225

Choose a tag to compare

6.0.1 (2024-09-26)

Bug Fixes

  • added a fix where secondary storage was not being provisioned
  • added a fix where workload_cluster_name and management_cluster_name outputs were not working (#889) (6e70225)

v6.0.0

20 Sep 09:15
v6.0.0
693c8e2

Choose a tag to compare

6.0.0 (2024-09-20)

Updates (#870) (693c8e2)

  • updated landing-zone-vsi module to 4.2.0
    • In previous versions, it was found that adding or removing VSIs after they have been initially created by this module can cause VSIs to be destroyed and recreated due to the naming convention and logic being used. In order to fix this, the naming convention has changed in v4 of the module to be prefix- + the last 4 digits of the subnet ID + a sequential number for each subnet. For example, prefix-3ad7-001.
  • Refactored the logic used to create OCP clusters. Its now using the base-ocp-vpc module
    • This module has some extra functionality which requires the runtime to have access to IBM Cloud private endpoints.

BREAKING CHANGES

  • If you were to upgrade the 'Red Hat OpenShift Container Platform on VPC landing zone' solution, or the 'VSI on VPC landing zone' from a previous version to this version, infrastructure will be destroyed and recreated. To prevent this, you should upgrade directly to version 6.8.1 which handles migration when upgrading the DA in projects.

v5.33.0

19 Sep 08:27
v5.33.0
b576712

Choose a tag to compare

5.33.0 (2024-09-19)

Features

  • added support to optionally pass an existing CBR zone ID in which all VPCs created will be added to (#745) (b576712)

v5.32.0

18 Sep 08:49
v5.32.0
3b9d896

Choose a tag to compare

5.32.0 (2024-09-18)

Features

  • added new input ignore_vpcs_for_cluster_deployment to the OCP standard DA to allow you to specify a VPC that you do not wish to create a cluster in. By default a cluster will be created in all of the VPCs specified in the vpcs input. (#881) (3b9d896)

v5.31.3

15 Sep 03:06
v5.31.3
2aeebc7

Choose a tag to compare

5.31.3 (2024-09-15)

Bug Fixes

  • deps: update required_provider to latest for the landing zone das (#878) (2aeebc7)

v5.31.2

10 Sep 01:22
v5.31.2
a6b3f6e

Choose a tag to compare

5.31.2 (2024-09-10)

Bug Fixes

  • added outputs for workload/management cluster names (#875) (a6b3f6e)

v5.31.1

07 Sep 07:15
v5.31.1
08bacf2

Choose a tag to compare

5.31.1 (2024-09-07)

Bug Fixes

  • deps: update terraform ibm to latest for the landing zone das (#872) (08bacf2)

v5.31.0

27 Aug 17:31
v5.31.0
6f65f1b

Choose a tag to compare

5.31.0 (2024-08-27)

Features

  • add outputs for cluster endpoint urls (#862)
    - added new outputs for cluster endpoints: public and private service endpoints, ingress subdomain, and web console (6f65f1b)

v5.30.1

27 Aug 13:15
v5.30.1
9fe2a93

Choose a tag to compare

5.30.1 (2024-08-27)

Bug Fixes

  • update the default VSI image name to ibm-ubuntu-24-04-minimal-amd64-4 (#861) (9fe2a93)

v5.30.0

27 Aug 09:04
v5.30.0
835d676

Choose a tag to compare

5.30.0 (2024-08-27)

Features

  • added support to the root level module cos input variable to configure management_events (true or false) in the activity_tracking configuration. The root level required IBM provider version constrains have been updated to >= 1.67.0, < 2.0.0 since this feature was only added in 1.67.0.(#847) (835d676)