---
name: vmwaresolutions-vc_deletingservices
title: Deleting services from 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: 2025-10-24
---

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

# Deleting services from VCF for Classic - Automated instances
{: #vc_deletingservices}

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 delete the services that were provisioned for your VMware Cloud Foundation for Classic - Automated instances when you no longer need these services.

## Before you delete services from Automated instances
{: #vc_deletingservices-prereq}

You are billed until the end of the IBM Cloud® infrastructure billing cycle for the deleted services.

## Procedure to delete services from Automated instances
{: #vc_deletingservices-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 delete services.
3. Click the **Services** tab.
4. On the **Services** page, locate the service instance that you want to delete, click the vertical overflow menu next to the **Status** column, and then click **Delete service**.
5. In the **Remove service** window, review the considerations or warnings if there are any and select **I Understand**. Click **Delete**.

## Results after you delete services from Automated instances
{: #vc_deletingservices-results}

After your request to delete a service is accepted, the service status is changed to **Removing**.

When the service deletion is completed successfully, you are notified by email, and the service is deleted from the **Services** page of the instance.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted services.
{: note}

## Manually removing the DNS entries for specific services
{: #vc_deletingservices-DNS-entries}

For specific services, if you installed the service in a VMware Solutions release earlier than V4.0 and you delete that service, you must manually remove the DNS entries.

After you delete the service, unused DNS entries remain in Active Directory™. These entries do not cause any problems. However, in the future, they might create conflicts with reverse lookups. It is recommended that you remove the entries as soon as possible.

The following table shows the services that are affected. The table also shows the pattern for hostnames for various service offerings. The actual hostname might differ from the pattern in various ways. Use the pattern to locate all of the registered DNS hostnames associated with a service. Many services have more than one registered hostname.

| Service | Hostname Pattern | Example |
|:-------- |:--------------------- | :----------- |
| Caveonix RiskForesight | `riskforesight` | `riskforesight`   \n `inst01-riskforesight` |
| F5 BIG-IP | `nickname-bigip1`   \n `nickname-bigip2` | `edgefw-bigip1` |
| FortigateVM | `nickname-fortigate` | `edgefw-fortigate01` |
| Entrust CloudControl™ | `htccnn-id` | `htcc02-GY67239` |
| Entrust DataControl® | `htdcnn-id` | `htcc02-GY67239` |
| Entrust KeyControl™ | `htkcnn-id` | `htcc02-GY67239` |
| VMware Aria Operations | `vrli`   \n `vrops`   \n `vrlog` | `vrli-master`   \n `vrops-data1`   \n `vrlog-master` |
{: caption="Hostname patterns and examples for affected services" caption-side="bottom"}

To remove the DNS entires, complete the following steps:

1. Log in to the Active Directory appliance and open the DNS tools.
2. Go to the instance subdomain, which is the subdomain under the root domain. Its name resembles the name of the Automated instance.
3. Remove the hostname entries for the specific deleted service appliances.
4. Open the associated reverse lookup table and remove the DNS entries from the table.

## Related links
{: #vc_deletingservices-related}

* [FAQ for VCF for Classic](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions&format=markdown)