[enterprise-4.10] MIG-1107 MTC 1.7 Release Notes

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]

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
 

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
 

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