This article is based on reporting from Red Hat Summit 2020 Virtual Experience, originally covered by CRN Australia (crn.com.au). Quotes are attributed to Red Hat executives as reported from that event.
Overview: An Open, Provider-Agnostic Hybrid Cloud Stack
Red Hat — acquired by IBM in 2019 but operating with significant autonomy — used its 2020 Summit to articulate a sharp and detailed strategy for leading the hybrid cloud market. The company’s thesis is straightforward: customers need an infrastructure stack that is open-source, consistent across environments, and invisible to application developers. Rather than locking customers into any single provider’s tooling, Red Hat bets that a vendor-neutral, community-driven platform will win enterprise adoption at scale.
Red Hat Summit 2020 was held as a virtual event due to the COVID-19 pandemic. Keynotes and panel discussions featured newly appointed CEO Paul Cormier alongside a wide roster of product and engineering leaders who walked through each layer of the company’s cloud strategy.
Layer 1: Red Hat Enterprise Linux as the Foundation
Red Hat Enterprise Linux (RHEL) remains the company’s flagship product and the base on which everything else is built. At Summit 2020, Red Hat made RHEL 8.2 generally available, adding enhanced monitoring capabilities and improved container support.
CEO Paul Cormier framed RHEL’s historical significance during his keynote panel: “Linux started an innovation cycle that continues in full force today” — through virtualization, cloud computing, containers, Kubernetes, and now edge computing.
Stephanie Chiras, Vice President and General Manager for RHEL, reinforced that point: “Linux provides the foundation upon which all this innovation is based.”
Gunnar Hellekson, Senior Director of Product Management and Strategy, noted that RHEL’s defining market advantage is operational consistency — the ability to deploy workloads reliably across on-premises data centers, multiple public clouds, and edge environments. That consistency, he argued, compounds in value as it propagates up through higher-order products in the Red Hat portfolio.
Tim Cramer, Vice President for Software Engineering, acknowledged a productive internal tension: OpenShift’s rapid growth is placing significant pressure on the RHEL roadmap, driving the operating system to evolve faster to support container-native and cloud-native workloads.
Layer 2: OpenShift as the Cloud-Era Platform
While RHEL built Red Hat’s reputation, OpenShift — the company’s enterprise Kubernetes platform — is the product Red Hat is betting on for long-term cloud dominance. At Summit 2020, Red Hat announced OpenShift 4.4 with a set of capabilities targeted at both near-term enterprise needs and emerging workloads.
Key OpenShift 4.4 Capabilities
- Kubernetes 1.17 implementation — bringing the platform in line with the upstream project.
- Advanced Cluster Management — simplifying administration of large, distributed Kubernetes deployments.
- Policy-based management — enabling dynamic scaling in environments that must respond rapidly to changing demand.
- OpenShift Virtualization — described by Matt Hicks, Executive Vice President for Products and Technologies, as the release’s “revolution.”
OpenShift Virtualization integrates the KubeVirt open-source project, allowing virtual machines (VMs) to be imported and run natively inside OpenShift alongside Kubernetes-managed containers. This removes a long-standing architectural divide: teams no longer have to choose between their existing VM-based infrastructure and a modern container platform. Hicks argued this bridges legacy infrastructure and cloud-native operations, reduces licensing overhead, and creates new pathways for industries — such as telecommunications preparing 5G deployments — that cannot immediately abandon their existing VM estates.
Layer 3: Open Hybrid Cloud as the Competitive Differentiator
Red Hat CTO Chris Wright described the hybrid cloud landscape as having expanded far beyond simple on-premises/public-cloud combinations. Infrastructure now spans data centers, multiple public clouds, and distributed edge nodes. Red Hat’s open-source portfolio — built on years of Linux, virtualization, and container development — positions the company to serve all of those environments with a consistent platform.
Wright also pointed to the next frontier: reducing the cognitive overhead on developers working in hybrid environments. New paradigms such as serverless computing and event-driven architectures are central to that goal, allowing teams to focus on application logic rather than infrastructure provisioning and management.
CEO Cormier was direct about what differentiates Red Hat: “This is what open, hybrid cloud is.” Kubernetes-centered innovation, he argued, has created the industry’s largest hybrid cloud ecosystem and placed Red Hat at its center.
Layer 4: Multi-Cloud as the Natural Evolution
Joe Fernandes, Vice President and General Manager for Core Cloud Platforms, noted that most Red Hat customers have already adopted hybrid infrastructure or are actively moving toward it. But the journey does not stop there — customers “then tend to move to a multi-cloud strategy.”
Mike Evans, Vice President for Technical Business Development, described the current environment as an “amalgamation of hybrid cloud, multi-cloud, and cloud-to-cloud” activity — with the expectation that complexity will increase rather than decrease.
Red Hat has cultivated deep partnerships with Amazon Web Services, Microsoft Azure, Google Cloud, and parent company IBM to support this multi-cloud reality. Evans also highlighted a notable industry trend: hyperscalers are themselves beginning to offer services that run on competitors’ clouds — Google’s Anthos and Microsoft’s Azure Stack being prominent examples. In effect, the large cloud providers are building their own cross-cloud hybrid strategies, which Evans argued validates Red Hat’s long-standing multi-cloud position.
Layer 5: Edge Computing as an Extension of Hybrid Cloud
CTO Wright acknowledged that “edge” is a broad and sometimes loosely defined concept, but framed it simply: putting computing closer to users and the data they need. CEO Cormier echoed that definition.
Joe Fitzgerald, Vice President and General Manager of Red Hat’s Management Business Unit, noted that edge workloads span multiple tiers — from cloud-adjacent aggregation nodes down to devices at the network perimeter. Red Hat’s focus, he said, is on the customer’s physical premises: the servers, gateways, and other hardware that organizations place at the edge of their networks.
The telecommunications industry is a particularly important edge use case. Verizon’s 5G buildout was highlighted during Cormier’s Summit keynote as an example of the scale and complexity involved. Fitzgerald described the technical challenge: managing a vast, geographically distributed computing infrastructure with enough speed and consistency to deliver next-generation network services.
Red Hat’s response involves extending real-time capabilities into the RHEL portfolio and OpenShift, enabling policy-based, automated management of distributed edge systems from a single consistent platform. As Fitzgerald summarized: “It’s all about speed and automation.”
The Kubernetes Maturity Curve
Five years after Google open-sourced Kubernetes, Brian Gracely, Senior Director for Product Strategy for OpenShift, argued the technology is entering a third generation of enterprise use cases. The first wave required deeply technical operations teams willing to navigate immature tooling without vendor support. The second wave brought broader enterprise adoption as the tooling stabilized. The third wave — now underway — is about making Kubernetes accessible to developers who are not infrastructure specialists at all.
Clayton Coleman, a Red Hat Solutions Architect for Containerized Application Infrastructure, framed the new challenges clearly: AI, machine learning, big data, and edge computing are the next frontiers. These workloads require domain experts — data scientists, ML engineers — who need to run complex infrastructure without becoming Kubernetes administrators.
The design goal for Red Hat’s Kubernetes platform, Coleman said, is maximum empathy for administrators and developers alike: clear guardrails, automated operators, and an ecosystem that puts teams on a well-defined path to production success. “We try to make it so Kubernetes is the easiest place to build and run applications,” he said.
VMs, Containers, and the VMware Comparison
Ashesh Badani, Senior Vice President for Cloud Platforms, addressed a question Red Hat executives frequently face: how does the company’s container strategy compare to VMware’s? Badani drew several distinctions:
- Kubernetes experience: Red Hat has shipped Kubernetes-based platforms for five years with a large installed customer base; VMware’s Kubernetes efforts, Badani argued, are comparatively nascent.
- Standards alignment: Red Hat’s platform is built on a Cloud Native Computing Foundation (CNCF) standardized Kubernetes stack. Badani characterized VMware as still deciding among multiple Kubernetes stacks, some of which are proprietary.
- Hybrid cloud architecture: Red Hat’s approach uses a consistent open stack across environments; VMware’s, Badani said, incorporates proprietary infrastructure per public cloud.
- VM and container convergence: Red Hat takes a cloud-native approach via KubeVirt and OpenShift Virtualization; Badani characterized the alternative as wrapping proprietary APIs around an existing virtualization platform.
- Open-source community: Red Hat has participated in open-source communities for over two decades, Badani noted, calling that depth of community engagement a genuine differentiator.
Note: These comparisons represent Red Hat’s own characterization of the competitive landscape as presented at its Summit. VMware’s perspective is not represented here.
Developer-First Infrastructure
A consistent theme across every layer of Red Hat’s strategy is that infrastructure should be invisible to the developers who use it. Fernandes stated it plainly: “Developers should be shielded from where those applications are running.”
Red Hat’s model — build once, package as a container, deploy anywhere — enables application teams to write code without caring whether it ultimately runs on-premises, on AWS, on Azure, or on Google Cloud. Administrators handle placement decisions; developers focus on the application.
This abstraction is especially important for specialized workloads. CTO Wright described how machine learning environments typically require hardware acceleration at the OS level, with OpenShift providing the abstraction layer that makes those accelerated resources accessible to data scientists without requiring them to understand the underlying infrastructure.
Cloud Provider Partnerships and Joint Engineering
Mike Farris, Vice President for Strategy, Products and Technologies, noted that Red Hat has focused not only on maturing its technology but on deepening its cloud provider partnerships. Even though the major hyperscalers offer their own container services, Evans said they recognize OpenShift as a platform their joint enterprise customers specifically request — particularly for migrating mission-critical applications or developing cloud-native workloads.
Enterprise customers are pressing cloud providers to offer jointly managed and, in some cases, jointly engineered solutions based on OpenShift — a dynamic already visible in Azure Red Hat OpenShift, a service co-engineered and co-supported by Microsoft and Red Hat. Farris indicated that similar deeper partnerships with other cloud providers were expected to follow.
COVID-19 Impact and Customer Support Measures
Cormier noted that the pandemic had limited operational impact on Red Hat’s engineering and product development, partly because a significant portion of the company’s engineers and developers already worked remotely before the crisis. “We’re going full force on the road map and product line we planned from the beginning,” he said.
Go-to-market activities requiring direct customer engagement proved more challenging to adapt. Red Hat responded with several customer-facing measures:
- Extended product life cycles — giving customers more time before being required to upgrade, reducing upgrade pressure during an already disruptive period.
- Reduced Technical Account Management costs — cutting prices for new customers by half.
- Free training programs — offered to furloughed workers and job seekers looking to build cloud and open-source skills.
Summary: The Five Pillars of Red Hat’s Hybrid Cloud Strategy
- RHEL as the universal foundation — operational consistency across every environment.
- OpenShift as the cloud-era platform — Kubernetes plus VM convergence, abstracted for developers.
- Open hybrid cloud — vendor-neutral, standards-based, bridging data center and cloud.
- Multi-cloud by design — deep partnerships with all major hyperscalers; provider-agnostic by architecture.
- Edge as hybrid cloud’s frontier — automated, policy-driven management of distributed infrastructure at scale.
Red Hat’s strategy depends on a coherent bet: that enterprise customers will prefer an open, consistent platform that works everywhere over any single provider’s proprietary stack. Whether the market ultimately rewards that approach will depend on execution — and on whether the open-source community continues to rally around the technologies Red Hat is building on.