---
name: vmwaresolutions-cr_orderinginstance-edge
title: Gateway cluster
description: As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2025-10-30
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Gateway cluster
{: #cr-orderinginstance-edge}

As of 17 July 2025, new automated installations of Red Hat&reg; OpenShift&reg; for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

 An edge gateway is required. You can bring your own gateway appliance or choose from one of the following options:

 * Gateway cluster with Juniper® vSRX
 * Gateway cluster with FortiGate® Virtual Appliance

 The gateway cluster is deployed in the same data center as the consolidated cluster.

The data center of the consolidated cluster must be available for gateway cluster deployment. Gateway cluster deployment is not supported for **Dallas 09**.
{: note}

## Cluster name
{: #cr-orderinginstance-edge-cluster-name}

The gateway cluster name is preset to **_instance name_-edge**.

CONTENT:

You can also specify a new cluster name that meets the following requirements:
* Only lowercase alphabetic, numeric, and hyphen (-) characters are allowed.
* The cluster name must start with a lowercase alphabetic character.
* The cluster name must end with a lowercase alphabetic or numeric character.
* The maximum length of the cluster name is 30 characters.
* The cluster name must be unique within the VMware Cloud Foundation for Classic - Automated instance.

## Compute capacity
{: #cr-orderinginstance-edge-compute-capacity}

For compute capacity, you get two cluster hosts and two 3.8 TB SSD storage.

## CPU model
{: #cr-orderinginstance-edge-cpu-model}

You can choose between the following CPU models:
* Dual Intel Xeon® Silver 4210 processor (Cascade Lake) with 20 cores, 2.20 GHz, and 10 Gb of uplink speed.
* Dual Intel Xeon Gold 5218 processor (Cascade Lake) with 32 cores, 2.30 GHz, and 25 Gb of uplink speed.

## RAM
{: #cr-orderinginstance-edge-ram}

You can select different values of RAM in the range 64 GB - 1.5 TB.

## Networking type
{: #cr-orderinginstance-edge-network-type}

Select either **Public and private network** or **Private network only** for the gateway cluster.

## Related links
{: #cr-orderinginstance-edge-related-links}

* [Procedure to order Cyber Recovery](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_orderinginstance-order-procedure&format=markdown)