---
name: vmwaresolutions-eos-kmip
title: End of Support for KMIP for VMware
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-09-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.

# End of Support for KMIP for VMware
{: #eos-kmip}

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}

**End of Marketing**: As of 17 July 2025, new deployments of VMware Regulated Workloads instances are no longer available for new customers. If you are an existing customer, you can still add or delete clusters, add or delete VMware ESXi™ servers or NFS storage, and add or remove services for your existing Regulated Workloads instances. As an existing customer, you can also view or delete your Regulated Workloads instances.
{: note}

Support for the Key Management Interoperability Protocol (KMIP™) for VMware® service will end on 31 December 2026 after which the service will no longer work. You must migrate to the native [IBM® Key Protect for IBM Cloud®](https://cloud.ibm.com/docs/key-protect?format=markdown) offering, or an alternative key management service of your choice by 31 December 2026.

If you are using the KMIP for VMware service, you must plan and start migration to [IBM® Key Protect for IBM Cloud®](https://cloud.ibm.com/docs/key-protect?format=markdown) services at the earliest.

The new key provider offering, [IBM® Key Protect for IBM Cloud®](https://cloud.ibm.com/docs/key-protect?format=markdown), has the following advantages over the KMIP for VMware adapter:
- Improved performance because the calls from KMIP to key provider are closer in network distance and no longer cross the service-to-service authorization boundaries.
- Improved visibility and management for the KMIP keys.
- No change in pricing.

To experience an improved performance at no additional cost, you must migrate to IBM® Key Protect for IBM Cloud® from KMIP for VMware service. For more information about KMIP migration, see [Migrating from KMIP for VMware to IBM Cloud native KMIP providers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip_migration&format=markdown).

Customers who are using vSphere version 7.x can encounter a Broadcom bug in vSphere HA that results in restart of virtual machines with vSphere encryption during the rekeying process. However, Broadcom provides a workaround for this issue. For more information about the workaround, see [Encrypted VM with Change Block Tracking (CBT) enabled unexpectedly powers off after shallow rekey operation](https://knowledge.broadcom.com/external/article?articleNumber=387897){: external}.
{: attention}

{{site.data.content.eol-ibm-cloud}}

## Related links
{: #eos-kmip-related}

* [IBM® Key Protect for IBM Cloud®](https://cloud.ibm.com/docs/key-protect?format=markdown)
* [Migrating from KMIP for VMware to IBM Cloud native KMIP providers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip_migration&format=markdown)
* [FAQ for KMIP for VMware migration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-kmip&format=markdown)