From 9db24c5ea3d40ea52379e2b7341d27ebf1a12146 Mon Sep 17 00:00:00 2001 From: Ronan Hennessy Date: Wed, 24 Sep 2025 14:40:52 +0100 Subject: [PATCH] TELCODOCS-2281: Release note for migration tool --- release_notes/ocp-4-20-release-notes.adoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/release_notes/ocp-4-20-release-notes.adoc b/release_notes/ocp-4-20-release-notes.adoc index 81a1773a16..135682da99 100644 --- a/release_notes/ocp-4-20-release-notes.adoc +++ b/release_notes/ocp-4-20-release-notes.adoc @@ -71,6 +71,20 @@ When you create a persistent volume (PV) by using the {lvms} Operator, the PV no The default namespace for the {lvms} Operator is now `openshift-lvm-storage`. You can still install {lvms} in a custom namespace. +[id="ocp-release-edge-computing-default-clusterinstance_{context}"] +==== SiteConfig CR to ClusterInstance CR migration tool + +{product-title} {product-version} introduces the `siteconfig-converter` tool to help migrate managed clusters from using a `SiteConfig` custom resource (CR) to a `ClusterInstance` CR. Using a `SiteConfig` CR to define a managed cluster is deprecated and will be removed in a future release. The `ClusterInstance` CR provides a more unified and generic approach to defining clusters and is the preferred method for managing cluster deployments in the {ztp} workflow. + +Using the `siteconfig-converter` tool, you can convert `SiteConfig` CRs to `ClusterInstance` CRs and then incrementally migrate one or more clusters at a time. Existing and new pipelines run in parallel, so you can migrate clusters in a controlled, phased manner and without downtime. + +[NOTE] +==== +The `siteconfig-converter` tool does not convert SiteConfig CRs that use the deprecated `spec.clusters.extraManifestPath` field. +==== + +For more information, see xref:../edge_computing/ztp-migrate-clusterinstance.adoc#ztp-migrate-clusterinstance[Migrating from SiteConfig CRs to ClusterInstance CRs]. + [id="ocp-release-notes-extensions_{context}"] === Extensions ({olmv1})