fix(deps): update terraform terraform-ibm-modules/landing-zone/ibm to v6

[terraform-ibm-modules-ops]

This PR contains the following updates:

Package	Type	Update	Change
terraform-ibm-modules/landing-zone/ibm (source)	module	major	5.24.3 -> 6.0.0

---

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)

v6.0.0

Compare Source

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. 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.

v5.33.0

Compare Source

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

Compare Source

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

Compare Source

Bug Fixes

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

v5.31.2

Compare Source

Bug Fixes

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

v5.31.1

Compare Source

Bug Fixes

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

v5.31.0

Compare Source

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

Compare Source

Bug Fixes

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

v5.30.0

Compare Source

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)

v5.29.1

Compare Source

Bug Fixes

• deps: update terraform ibm to latest for the landing zone das (#​835) (f69aed8)

v5.29.0

Compare Source

Features

• the following optional input variables have been added to the OCP DA solution, allowing the use of existing resources for KMS and COS:
  - existing_kms_instance_name
  - existing_kms_resource_group
  - existing_kms_endpoint_type
  - existing_cos_instance_name
  - existing_cos_resource_group
  - existing_cos_endpoint_type
  - use_existing_cos_for_vpc_flowlogs
  - use_existing_cos_for_atracker (#​855) (1ed856b)

v5.28.0

Compare Source

Features

• added support to specify the operating system for OCP cluster workers using new input operating_system (#​848) (9eda4cd)

v5.27.1

Compare Source

Bug Fixes

• fixed the resource_group_names and resource_group_data outputs to ensure they include prefix (#​852) (677a996)

v5.27.0

Compare Source

Features

• removed support for provisioning a lite plan COS instance as this plan is no longer available in IBM Cloud (#​844) (006e35f)

v5.26.0

Compare Source

Features

• added new output vpc_dns (#​842) (9f87d9d)

v5.25.2

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.19.0 (#​839) (f4b278b)

v5.25.1

Compare Source

Bug Fixes

• added a fix to handle the new ibm-storage-operator addon which comes installed by default on OCP 4.15 cluster (#​838) (e02f396)

v5.25.0

Compare Source

Features

• add new input variable kms_wait_for_apply to make terraform wait until KMS is applied to cluster master and it is ready and deployed. Default value is true. (#​833) (5b2b644)

v5.24.7

Compare Source

Bug Fixes

• update the default VSI image name to ibm-ubuntu-24-04-minimal-amd64-2 (#​819) (8c3eae4)

v5.24.6

Compare Source

Bug Fixes

• deps: update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.18.3 (#​821) (4feb90e)

v5.24.5

Compare Source

Bug Fixes

• remove upper limit for required terraform version (#​810) (f32e51d)

v5.24.4

Compare Source

Bug Fixes

• deps: update terraform ibm to latest for the landing zone das (#​802) (12b95d0)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[terraform-ibm-modules-dev]

/run pipeline