v1.2.1

Patch Updates

1. Separated LoadBalancers for API and *.apps Traffic

Updated the Terraform code to provision distinct LoadBalancers for the OpenShift API and Ingress (*.apps) endpoints. This improves security isolation, scalability, and access control by separating control-plane and application traffic. The compute, DNS, and load balancer modules were modified accordingly, along with updates to both create-cluster and add-nodes stacks to ensure correct backend associations for new nodes.

v1.2.0

Enhancements

1. Cluster Networking Configuration

Reconfigured the default networking setup to support OpenShift clusters with both VM and Bare Metal nodes. The stack now reserves two subnets during initial installation: one for iSCSI traffic (private_subnet_bare_metal) and one for general cluster traffic (private_subnet_opc). This enables consistent VNIC assignments and allows adding VM or Bare Metal nodes to an existing cluster without additional network changes. Image creation logic has also been updated to support the required launch modes for each instance type.

2. Tag Namespace Validation

Added validation to ensure the tag namespace used for OpenShift clusters follows the expected format required by the platform. This helps the underlying infrastructure correctly identify and manage OpenShift resources during installation. Descriptions have also been updated to guide users in providing a valid namespace.

3. Default Shape Compatibility Alignment

Updated the default compute shape from VM.Standard.E4.Flex to VM.Standard.E5.Flex to align with current platform support and ensure successful resource provisioning.

v1.1.1

Bug Fixes

1. Tags created in non-home regions

There was an issue related to tag creation behavior in non-home regions. This fix resolves the problem where defined tags were not being created correctly in regions outside the tenancy's home region and allows for tag creation in all regions.

What's Changed

• release-v1.1.0 minor fix by @nikhisin3001 in #59
• Fix add nodes stack by @nikhisin3001 in #60
• add missing doc link to RWX-LA readme by @dfoster-oracle in #61
• release v1.1.1 by @nikhisin3001 in #62

Full Changelog: v1.1.0...v1.1.1

v1.1.0

New Features

1. Tagging Workflow Introduced Prior to Cluster Deployment

A new tagging structure has been introduced to ensure consistent resource attribution across OpenShift deployments. Before launching any new OpenShift clusters, users must now run the create-resource-attribution-tags stack to predefine the required tags. This change improves governance, tracking, and lifecycle management of OpenShift resources in OCI.
⚠️ Important: You must run the create-resource-attribution-tags stack before running any other stacks. This stack creates a tagNamespace and associated defined-tags (openshift-tags and openshift-resource) that are essential for all subsequent stacks to function correctly. Skipping this step may cause failures or unexpected behavior. You can skip this step if the tagNamespace and its associated defined-tags already exist.

2. Red Hat OpenShift Virtualization Now in Limited Availability (LA) on OCI

Initial support for Red Hat OpenShift Virtualization on Oracle Cloud Infrastructure is now available under Limited Availability. This enables customers to run virtual machine workloads alongside containers within the same OpenShift environment. As this feature is in LA, some limitations and issues may occur — please contact the team to report feedback. Link

3. Support for Both Multi-AD and Single-AD Cluster Deployments

The Terraform stack now supports more flexible deployment options across Availability Domains. Users can now deploy OpenShift clusters in either a single AD or multi-AD setup, improving high availability and alignment with varied customer infrastructure needs.

Enhancements

1. Support for OpenShift on OCI Bare Metal GPU Shapes in Limited Availability (LA)

Enhancements have been made to the Terraform stack to support launching OpenShift clusters on OCI Bare Metal instances with GPU shapes. This update includes refining shape-matching logic to ensure GPU-capable nodes are properly identified and provisioned. The shapes supported are A100 and H100. As this feature is in LA, some limitations and issues may occur — please contact the team to report feedback.

Fixes

1. Bug Fix: Incorrect pod-security.kubernetes.io/enforce-version Label Value

Addressed an issue where the pod-security.kubernetes.io/enforce-version label was present but set to an incorrect value in certain namespaces. This could cause unexpected behavior with Kubernetes Pod Security Admission (PSA) policies. The label value is now correctly set during cluster provisioning to ensure proper enforcement and compliance with security standards.

v1.0.0

What's Changed

• Upgraded OCI CCM and CSI driver versions to v1.30
  • Adds support for using Bare Metal instances as OpenShift cluster nodes
  • Adds support for provisioning Raw Block Volumes (no filesystem)
• Major Terraform refactor
  • Instead of one infrastructure.tf file that can only create a cluster, we now have the terraform-stacks directory which contains individual Terraform stacks intended to be used with RMS:
    • add-nodes
    • create-cluster
    • create-tags
  • Use shared_modules across all Terraform stacks
  • Packaging of stacks into versioned and distributable zip files
• Terraform improvements
  • Instances are now distributed across Availability and Fault Domains if available
  • create-cluster stack can be used for a connected Agent-based installation
  • Stacks now output a dynamic_custom_manifest which contains all custom manifests necessary for OpenShift installation, pre-formatted with OCI CCM and CSI secrets, and condensed into a single manifest for easy uploading/pasting
• New custom manifests
  • All necessary custom manifests are now formatted and output by the Terraform stacks
  • oci-eval-user-data.yml executes scipts uploaded during instance creation
    • iscsi-oci-configure-secondary-nic.sh evaluates and configures the instance network settings for iSCSI boot volumes (Bare Metal)
  • cluster-network.yml modifies the default cluster Network subnet to avoid conflicts with iSCSI boot volumes in OCP 4.17+
• Versioned OCI CCM and CSI manifests
  • Add support for updating CCM and CSI drivers on an existing cluster