Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Yes. Red Hat documented deploying Red Hat Gluster Storage on Google Cloud Platform (now commonly called Google Cloud), using Google Compute Engine virtual machines and persistent disks. That is a historical deployment pattern, not a currently supported Red Hat offering: Red Hat Gluster Storage reached end of life on December 31, 2024.

How the documented Google Cloud deployment worked

Red Hat described Gluster Storage as a software-defined storage platform and documented a custom Gluster Storage image running on Google Compute Engine (GCE). The deployment used virtual machines and persistent disks to provide shared file storage. The versioned procedure covered planning, converting and importing the image, preparing disks, configuring volumes, setting up geo-replication, and connecting clients. It required a Google account, Google Cloud SDK, and access to Red Hat Gluster Storage software channels. See Red Hat’s Gluster Storage 3.5 Public Cloud Deployment Guide.

The guide is useful for understanding the architecture Red Hat documented; its setup steps and cloud specifications should not be treated as current instructions or limits.

What architecture did Red Hat describe?

The guide’s reference design targeted roughly 100 TB of usable storage. It used two-way synchronous replication between zones in a primary storage pool, plus asynchronous geo-replication to a secondary pool in another region for disaster recovery. Its historical topology was a 10 x 2 distribute-replicate design. These are parameters of the guide’s example, not independent performance results or a promise of capacity on Google Cloud today.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Red Hat advised tuning the design to the workload and testing performance and scale for the intended use case. Its compatibility guidance named Google Cloud n1-highmem-4 as a recommended minimum instance type for production Gluster Storage cloud deployments. Because the product is end of life and cloud specifications may change, that recommendation is historical compatibility guidance—not present-day sizing advice. See Red Hat’s Gluster Storage compatibility guidance.

Is Red Hat Gluster Storage still supported?

No. Red Hat says Gluster Storage reached end of life on December 31, 2024, and that version 3.5 was its final supported series. The lifecycle notice states that the product’s support lifecycle ended on that date. Red Hat directs customers to contact their sales representative to discuss modernization and migration options. See the Red Hat Gluster Storage lifecycle policy.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What should operators of a legacy deployment do?

If you still run this configuration, confirm your support position with Red Hat and plan a migration with Red Hat or a qualified infrastructure provider. Treat the old deployment guide as historical design documentation, not a recipe to recreate or expand a production system. A migration review should account for workload needs, failure-domain isolation, replication and disaster-recovery objectives, and the operational work involved in maintaining a custom image.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.