From 2b8d1789050f46fce5b2926b634e847fe6661a31 Mon Sep 17 00:00:00 2001 From: stoobie Date: Thu, 24 Mar 2022 18:30:18 +0200 Subject: [PATCH] MIG-1107 MTC 1.7 Release Notes --- .../mtc-release-notes.adoc | 8 ++++-- modules/migration-mtc-release-notes-1-4.adoc | 13 ---------- modules/migration-mtc-release-notes-1-5.adoc | 4 +-- modules/migration-mtc-release-notes-1-6.adoc | 4 +-- modules/migration-mtc-release-notes-1-7.adoc | 26 +++++++++++++++++++ 5 files changed, 34 insertions(+), 21 deletions(-) delete mode 100644 modules/migration-mtc-release-notes-1-4.adoc create mode 100644 modules/migration-mtc-release-notes-1-7.adoc diff --git a/migration_toolkit_for_containers/mtc-release-notes.adoc b/migration_toolkit_for_containers/mtc-release-notes.adoc index 09582b01deea..0b763f867b7d 100644 --- a/migration_toolkit_for_containers/mtc-release-notes.adoc +++ b/migration_toolkit_for_containers/mtc-release-notes.adoc @@ -6,12 +6,16 @@ include::_attributes/common-attributes.adoc[] toc::[] -The {mtc-full} ({mtc-short}) enables you to migrate application workloads between {product-title} clusters at the granularity of a namespace. +The release notes for {mtc-full} ({mtc-short}) describe new features and enhancements, deprecated features, and known issues. + +The {mtc-short}) enables you to migrate application workloads between {product-title} clusters at the granularity of a namespace. You can migrate from xref:../migrating_from_ocp_3_to_4/about-migrating-from-3-to-4.adoc[{product-title} 3 to {product-version}] and between {product-title} 4 clusters. {mtc-short} provides a web console and an API, based on Kubernetes custom resources, to help you control the migration and minimize application downtime. +For information on the support policy for {mtc-short}, see link:https://access.redhat.com/support/policy/updates/openshift#app_migration[OpenShift Application and Cluster Migration Solutions], part of the _Red Hat {product-title} Life Cycle Policy_. + +include::modules/migration-mtc-release-notes-1-7.adoc[leveloffset=+1] include::modules/migration-mtc-release-notes-1-6.adoc[leveloffset=+1] include::modules/migration-mtc-release-notes-1-5.adoc[leveloffset=+1] -include::modules/migration-mtc-release-notes-1-4.adoc[leveloffset=+1] diff --git a/modules/migration-mtc-release-notes-1-4.adoc b/modules/migration-mtc-release-notes-1-4.adoc deleted file mode 100644 index c4f641304dda..000000000000 --- a/modules/migration-mtc-release-notes-1-4.adoc +++ /dev/null @@ -1,13 +0,0 @@ -// Module included in the following assemblies: -// -// * migration_toolkit_for_containers/mtc-release-notes.adoc - -[id="migration-mtc-release-notes-1-4_{context}"] -= {mtc-full} 1.4 release notes - -The release notes for {mtc-full} ({mtc-short}) version 1.4 describe new features, enhancements, and known issues. - -[id="known-issues-1-4_{context}"] -== Known issues - -* MTC 1.4.6 cannot be deployed on {product-title} 3.9 (link:https://bugzilla.redhat.com/show_bug.cgi?id=1981794[*BZ#1981794*]) or 3.10 (link:https://bugzilla.redhat.com/show_bug.cgi?id=1981537[*BZ#1981537*]). diff --git a/modules/migration-mtc-release-notes-1-5.adoc b/modules/migration-mtc-release-notes-1-5.adoc index e9a187a489ca..2f61531c7c38 100644 --- a/modules/migration-mtc-release-notes-1-5.adoc +++ b/modules/migration-mtc-release-notes-1-5.adoc @@ -1,12 +1,10 @@ // Module included in the following assemblies: // // * migration_toolkit_for_containers/mtc-release-notes.adoc - +:_content-type: REFERENCE [id="migration-mtc-release-notes-1-5_{context}"] = {mtc-full} 1.5 release notes -The release notes for {mtc-full} ({mtc-short}) version 1.5 describe new features, enhancements, and known issues. - [id="new-features-and-enhancements-1-5_{context}"] == New features and enhancements diff --git a/modules/migration-mtc-release-notes-1-6.adoc b/modules/migration-mtc-release-notes-1-6.adoc index caa992eed7a0..33dae42d221e 100644 --- a/modules/migration-mtc-release-notes-1-6.adoc +++ b/modules/migration-mtc-release-notes-1-6.adoc @@ -1,12 +1,10 @@ // Module included in the following assemblies: // // * migration_toolkit_for_containers/mtc-release-notes.adoc - +:_content-type: REFERENCE [id="migration-mtc-release-notes-1-6_{context}"] = {mtc-full} 1.6 release notes -The release notes for {mtc-full} ({mtc-short}) version 1.6 describe new features and enhancements, deprecated features, and known issues. - [id="new-features-and-enhancements-1-6_{context}"] == New features and enhancements diff --git a/modules/migration-mtc-release-notes-1-7.adoc b/modules/migration-mtc-release-notes-1-7.adoc new file mode 100644 index 000000000000..4dfb20100ed0 --- /dev/null +++ b/modules/migration-mtc-release-notes-1-7.adoc @@ -0,0 +1,26 @@ + +// Module included in the following assemblies: +// +// * migration_toolkit_for_containers/mtc-release-notes.adoc +:_content-type: REFERENCE +[id="migration-mtc-release-notes-1-7_{context}"] += {mtc-full} 1.7 release notes + +[id="new-features-and-enhancements-1-7_{context}"] +== New features and enhancements + +This release has the following new features and enhancements: + +* The {mtc-full} ({mtc-short}) Operator now depends upon the OpenShift API for Data Protection (OADP) Operator. When you install the {mtc-short} Operator, the Operator Lifecycle Manager (OLM) automatically installs the OADP Operator in the same namespace. + +* You can migrate from a source cluster that is behind a firewall to a cloud-based destination cluster by establishing a network tunnel between the two clusters by using the `crane tunnel-api` command. + +* Converting storage classes in the MTC web console: You can convert the storage class of a persistent volume (PV) by migrating it within the same cluster. + +[id="known-issues-1-7_{context}"] +== Known issues + +This release has the following known issues: + +* `MigPlan` custom resource does not display a warning when an AWS gp2 PVC has no available space. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1963927[*BZ#1963927*]) +* Block storage for IBM Cloud must be in the same availability zone. See the link:https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-faq[IBM FAQ for block storage for virtual private cloud].