At a Glance
- Red Hat OpenShift now integrates directly with the Google Cloud console, reducing onboarding friction for new cluster provisioning
- OpenShift Virtualization reaches general availability on OpenShift Dedicated on Google Cloud, running on C3 bare-metal instances for direct CPU and memory access
- Pay-as-you-go billing through Google Cloud Marketplace merges Red Hat subscription costs against overall Google Cloud spend on a single invoice
- VMs, containers, and serverless workloads become manageable from one Kubernetes-native interface, using one toolset and one set of operational practices
Enterprises running aging VM infrastructure have one concrete exit path in 2026, and Red Hat just widened it significantly. On March 26 at KubeCon + CloudNativeCon EU in Amsterdam, Red Hat and Google Cloud announced an expanded collaboration that places OpenShift directly inside the Google Cloud console and makes OpenShift Virtualization generally available on OpenShift Dedicated, eliminating the previous requirement to navigate separate portals and provisioning flows for what should be a unified workload.
What this actually changes for IT teams isn’t just convenience. Running OpenShift Virtualization on Google Cloud’s C3 bare-metal instances means workloads get direct access to CPU and memory, bypassing the hypervisor layer entirely, which matters acutely for performance-sensitive workloads and for software with restrictive per-core licensing models.
OpenShift Inside the Google Cloud Console: What Actually Changed
Most reviewers are framing this as a partnership announcement. It’s more precise to call it an architectural consolidation.
Previously, provisioning Red Hat OpenShift Dedicated on Google Cloud required navigating between the Red Hat Hybrid Cloud Console and the Google Cloud interface to complete prerequisites and configure clusters. Now, OpenShift Dedicated users can natively validate Google Cloud prerequisites before transitioning to a guided cluster provisioning flow within the Red Hat Hybrid Cloud Console, triggered from inside the Google Cloud console itself.
Billing consolidation alone removes a persistent headache at enterprise scale. Pay-as-you-go procurement through Google Cloud Marketplace applies the Red Hat subscription cost against total Google Cloud spend, generating a single invoice instead of two parallel billing cycles. For Indian enterprises already running multi-cloud environments with GCP as the anchor cloud, this directly reduces procurement complexity with finance and vendor management teams.
Why Bare Metal Matters for VM Migrations in 2026
Running VMs on a hypervisor-within-a-hypervisor stack extracts a performance penalty that most migration documentation quietly glosses over.
OpenShift Virtualization on Google Cloud C3 bare-metal instances bypasses this entirely. Workloads get direct access to hardware-level CPU and memory resources, which is critical for performance-sensitive applications and any software under per-socket or per-core licensing constraints. “Customers now have a smoother path, enabling them to run both virtualised and containerized workloads consistently on Google Cloud’s global, secure, and performant infrastructure,” said Nirav Mehta, Vice President of Product Management for Google Cloud Compute Platform at Google Cloud.
And the operational shift deserves attention from teams managing mixed environments. “Red Hat’s hybrid cloud vision is built on consistency, the ability to run any workload, anywhere, with the same operational model,” said Mike Barrett, Vice President and General Manager of Hybrid Cloud Platforms at Red Hat. That consistency extends to tooling, RBAC, and Day 2 operations, not just the deployment interface.
5 Capabilities This Expansion Unlocks for Enterprise Teams
- Unified workload management across VMs, containers, and serverless workloads from a single Kubernetes interface, using one toolset and operational practice set
- Native Google Cloud service integrations, giving OpenShift workloads direct support for Google Cloud Secret Manager, Certificate Authority Service, and Workload Identity Federation
- Migration Toolkit for Virtualization bundled in, reducing the hands-on effort required to map and transfer VM storage and networking configurations during migration
- Ansible Automation Platform integration included, targeting Day 2 operations and reducing manual intervention in cluster management post-deployment
- Smart GPU allocation introduced in OpenShift 4.21, extending AI workload placement decisions to GPU resources across hybrid infrastructure
Testing Revealed a Capability Gap Nobody Talks About
The onboarding flow improvement is real, but the prerequisite validation step exposes a subtle constraint worth naming directly.
During our March 2026 test provisioning, the native Google Cloud console prerequisite check correctly flagged insufficient IAM permissions on the first attempt before the cluster flow even began. This sounds minor. But for organizations with rigid IAM governance structures, common in BFSI and government-adjacent enterprises across India, the pre-flight check shifts debugging time from post-deployment to pre-deployment. That’s a fundamentally different failure mode, and it’s faster to resolve.
But the hybrid management capability does not yet deliver fully automated bidirectional workload mobility between on-premises OpenShift and Google Cloud OpenShift Dedicated. Consistent platform, yes. Live workload portability without manual intervention, not yet. Teams planning multi-region failover architectures should account for that gap in current deployment designs.
Where It Falls Short
OpenShift Virtualization on Google Cloud currently requires C3 bare-metal instances, which carry a cost premium over standard compute. For smaller organizations or teams running primarily containerized workloads with no legacy VM estate, the value proposition narrows considerably. For current pricing on OpenShift Dedicated and bare-metal C3 instances, contact Google Cloud or Red Hat directly, as rates vary by region, commitment tier, and procurement channel, and published list prices from prior years do not reflect 2026 commercial terms.
