Releases: terraform-ibm-modules/terraform-ibm-landing-zone
Releases · terraform-ibm-modules/terraform-ibm-landing-zone
v6.0.3
v6.0.2
v6.0.1
v6.0.0
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
.
- 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
- 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. A fully supported migration method will be available shortly. If re-creating infrastructure is going to impact day-to-day operations, we suggest to hold off upgrading to this version until there is a fully supported migration path.