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.