v7.4.2

7.4.2 (2025-03-27)

Bug Fixes

• add missing endpoint_type to the ibm_cos_bucket_lifecycle_configuration (#971) (ab18ca2)

v7.4.1

7.4.1 (2025-03-25)

Bug Fixes

• deps: update terraform ibm to latest for the landing zone das (#968) (d6d992c)

v7.4.0

7.4.0 (2025-03-24)

Features

• add the ability to disable / enable the OCP console using new parameter in clusters input enable_ocp_console.

• Removed the import_default_worker_pool_on_create parameter in clusters input. The allow_default_worker_pool_replacement parameter will now use the orphan_on_delete provider functionality. For more info, see https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc?tab=readme-ov-file#important-considerations-for-terraform-and-default-worker-pool (#960) (5d9d80b)

v7.3.2

7.3.2 (2025-03-20)

Bug Fixes

• update the default VSI image name to ibm-ubuntu-24-04-2-minimal-amd64-1 (#966) (898a009)

v7.3.1

7.3.1 (2025-03-12)

Bug Fixes

• deps: update terraform ibm to latest for the landing zone das (#964) (411dcce)

v7.3.0

7.3.0 (2025-02-25)

Features

• updated the vpcs input in the root level module to support extra DNS configuration using new attributes: dns_records, dns_zone_label, dns_zone_description, and dns_zone_name (#956) (44a6648)

v7.2.2

7.2.2 (2025-02-21)

Bug Fixes

• fix COS lifecycle bug (#957) (9f89ff4)

v7.2.1

7.2.1 (2025-02-21)

Bug Fixes

• deps: update terraform ibm to latest for the landing zone das (#952) (87b1dab)

v7.2.0

7.2.0 (2025-02-20)

Features

• Removed the logic that creates a virtual private endpoint for COS since it was clashing with the one created by VPC clusters and breaking cluster communication from worker nodes to the COS direct endpoint. When upgrading from an older version, you will see the expected destroy of the virtual private endpoint for COS and its associated reserved IP (#954) (5c64cf1)

v7.1.0

7.1.0 (2025-02-20)

Features

• updated configuration to use the new ibm_cos_bucket_lifecycle_configuration for managing lifecycle configuration for a bucket since the legacy approach is now deprecated. Migrating to the new schema addresses the limitations where one cannot create a rule with same rule id that has transition, expiration and abort_incomplete simultaneously, and not being able to create multiple abort_incomplete_multipart_upload rules. (#944) (db96a4b)