---
name: vmwaresolutions-vc_addingnfs
title: Adding NFS storage to VCF for Classic - Automated instances
description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® 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: 2026-01-21
---

> ## 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.

# Adding NFS storage to VCF for Classic - Automated instances
{: #vc_addingnfs}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® 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}

You can expand the capacity of your VMware Cloud Foundation for Classic - Automated instance according to your business needs by adding Network File System (NFS) storage.

## Before you add NFS storage to Automated instances
{: #vc_addingnfs-prereq}

* Do not add NFS storage from the VMware vSphere® Web Client. The changes that you make on the vSphere Web Client are not synchronized with the IBM Cloud® for VMware Solutions console.
* IBM does not manage NFS file shares that you add manually to an instance.
* You can add or remove NFS storage shares to or from an existing NFS or vSAN cluster.
* If you mount IBM Cloud Endurance NFS storage to your cluster, consider the following steps:
   * Ping the NFS server for the storage and note the subnet for the server IP address.
   * Review the VMKernel adapters for the hosts that will use the storage and make note of the subnet for `vmk3`. Use the **File Storage** list to authorize the `vmk3` subnet to access the NFS datastore.
   * Review the static routes defined on the hosts with the `esxcli network ip route ipv4 list` command. A static route must be displayed for the NFS server IP subnet to the gateway for the `vmk3` subnet listed in the previous step.

## Procedure to add NFS storage to Automated instances
{: #vc_addingnfs-procedure}

1. In the VMware Solutions console, click **Licensing and metering > Add-on services** from the left navigation panel.
2. In the **VMware Cloud Foundation for Classic** table, click the instance for which you want to expand capacity.
3. Click the **Infrastructure** tab.
4. In the **Clusters** table, click the cluster to which you want to add NFS storage.
5. In the **Storage** section, click **Add**.
6. In the **Add NFS storage** side pane, complete the storage configuration.
   * To add and configure the same settings to all file shares, specify the **Number of shares**, **Size (GB)**, and **Performance**.
   * To add and configure file shares individually, toggle the **Configure shares individually** switch on. Then, click **Add shared storage** and select the **Size (GB)** and **Performance** for each individual file share. You must select at least one file share. For more information, see [NFS storage](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-consold-cluster&format=markdown#vc_orderinginstance-nfs-storage).
7. Review the estimated price and click **Add**.

## Results after you add NFS storage to Automated instances
{: #vc_addingnfs-results}

1. You might experience a slight delay on the console while the instance status changes from **Available** to **Modifying**. Allow the operation to complete before you make more changes to the instance.
2. You are notified by email that your request to add NFS storage is being processed. On the console, the status of the cluster that is associated with the NFS storage is changed to **Modifying**.
3. If you do not see that the new NFS storage is added to the list in the cluster, check your email or view the console notifications to find more details.

## Related links
{: #vc_addingnfs-related}

* [VCF for Classic - Automated BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom&format=markdown)
* [Planning for Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_planning&format=markdown)
* [Requirements for Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req&format=markdown)
* [Adding clusters to Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters&format=markdown)
* [Place a host in maintenance mode](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vsphere-resource-management/using-drs-clusters-to-manage-resources/removing-hosts-from-a-cluster/place-a-host-in-maintenance-mode.html){: external}