openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

TELCODOCS-2281: Release note for migration tool

Browse Source
This commit is contained in:
Ronan Hennessy
2025-09-24 14:40:52 +01:00
parent d396051428
commit 9db24c5ea3
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
release_notes/ocp-4-20-release-notes.adoc
View File

@@ -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})