Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
    2. history bug_report picture_as_pdf
×

What’s new with OpenShift Dedicated

With its foundation in Kubernetes, OpenShift Dedicated is a complete OpenShift Container Platform cluster provided as a cloud service, configured for high availability, and dedicated to a single customer.

OpenShift Dedicated is professionally managed by Red Hat and hosted on Google Cloud Platform (GCP) or Amazon Web Services (AWS). Each OpenShift Dedicated cluster includes a fully managed control plane (Control and Infrastructure nodes), application nodes, installation and management by Red Hat Site Reliability Engineers (SRE), premium Red Hat Support, and cluster services such as logging, metrics, monitoring, notifications portal, and a cluster portal.

OpenShift Dedicated clusters are available on the Hybrid Cloud Console. With the Red Hat OpenShift Cluster Manager application, you can deploy OpenShift Dedicated clusters to either on-premises or cloud environments.

New changes and updates

Q4 2024

  • Workload Identity Federation (WIF) authentication type is now available. OpenShift Dedicated on Google Cloud Platform (GCP) customers can now use WIF as an authentication type when creating a cluster. WIF is a GCP Identity and Access Management (IAM) feature that provides third parties a secure method to access resources on a customer’s cloud account. WIF is Google Cloud’s preferred method for credential authentication.

    For more information, see Creating a cluster on GCP with Workload Identity Federation.

  • Private Service Connect (PSC) networking feature is now available. You can now create a private OpenShift Dedicated cluster on Google Cloud Platform (GCP) using Google Cloud’s security-enhanced networking feature Private Service Connect (PSC).

    PSC is a capability of Google Cloud networking that enables private communication between services across different GCP projects or organizations. Implementing PSC as part of your network connectivity allows you to deploy OpenShift Dedicated clusters in a private and secured environment within GCP without using any public-facing cloud resources.

    For more information, see Creating a GCP Private Service Connect enabled private cluster.

Q3 2024

  • Support for GCP A2 instance types with A100 80GB GPUs. OpenShift Dedicated on Google Cloud Platform (GCP) now supports A2 instance types with A100 80GB GPUs. These instance types meet the specific requirements listed by IBM Watsonx.ai. For more information, see Google Cloud compute types.

  • Expanded support for GCP standard instance types. OpenShift Dedicated on Google Cloud Platform (GCP) now supports standard instance types for control plane and infrastructure nodes. For more information, see Control plane and infrastructure node sizing and scaling.

  • OpenShift Dedicated regions added. OpenShift Dedicated on Google Cloud Platform (GCP) is now available in the following additional regions:

    • Melbourne (australia-southeast2)

    • Milan (europe-west8)

    • Turin (europe-west12)

    • Madrid (europe-southwest1)

    • Santiago (southamerica-west1)

    • Doha (me-central1)

    • Dammam (me-central2)

    For more information about region availabilities, see Regions and availability zones.

Q2 2024

  • Cluster delete protection. OpenShift Dedicated on Google Cloud Platform (GCP) users can now enable the cluster delete protection option, which helps to prevent users from accidentally deleting a cluster. For more information, see Creating a cluster on GCP with CCS.

  • CSI Operator update. OpenShift Dedicated is capable of provisioning persistent volumes (PVs) using the Container Storage Interface (CSI) driver for Google Compute Platform (GCP) Filestore Storage. For more information, see Google Compute Platform Filestore CSI Driver Operator.

  • Support for new GCP instances. OpenShift Dedicated now supports more worker node types and sizes on Google Cloud Platform. For more information, see Google Cloud compute types.

Q1 2024

  • OpenShift Dedicated regions added. OpenShift Dedicated on Google Cloud Platform (GCP) is now available in the Delhi, India (asia-south2) region. For more information on region availabilities, see Regions and availability zones.

  • Policy constraint update. OpenShift Dedicated on Google Cloud Platform (GCP) users are now allowed to deploy clusters with the constraints/iam.allowedPolicyMemberDomains constraint in place. This feature allows users to restrict the set of identities that are allowed to be used in Identity and Access Management policies, further enhancing overall security for their resources.

Q4 2023

  • Policy constraint update. OpenShift Dedicated on Google Cloud Platform (GCP) users can now enable UEFISecureBoot during cluster installation, as required by the GCP ShieldVM policy. This new feature adds further protection from boot or kernel-level malware or rootkits.

  • Cluster install update. OpenShift Dedicated clusters can now be installed on Google Cloud Platform (GCP) shared VPCs. For more information, see Creating a cluster on GCP with CCS.

  • OpenShift Dedicated on Google Cloud Marketplace availability. When creating an OpenShift Dedicated (OSD) cluster on Google Cloud through the Hybrid Cloud Console, customers can now select Google Cloud Marketplace as their preferred billing model. This billing model allows Red Hat customers to take advantage of their Google Committed Use Discounts (CUD) towards OpenShift Dedicated purchased through the Google Cloud Marketplace. For more information, see Creating a cluster on GCP with Google Cloud Marketplace.

Known issues

  • OpenShift Container Platform 4.14 introduced an updated HAProxy image from 2.2 to 2.6. This update created a change in behavior enforcing strict RFC 7230 compliance, rejecting requests with multiple Transfer-Encoding headers. This may cause exposed pods in OpenShift Dedicated 4.14 clusters sending multiple Transfer-Encoding headers to respond with a 502 Bad Gateway or 400 Bad Request error. To avoid this issue, ensure that your applications are not sending multiple Transfer-Encoding headers. For more information, see Red Hat Knowledgebase article. (OCPBUGS-43095)