Skip to content

Commit e164213

Browse files
authored
Merge pull request #35886 from apinnick/mtc-rn
MTC 1.5.1 RN
2 parents 8db3429 + 7a0a3cb commit e164213

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed

modules/common-attributes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ endif::[]
4242
:mtc-short: MTC
4343
:mtc-full: Migration Toolkit for Containers
4444
:mtc-version: 1.5
45-
:mtc-version-z: 1.5.0
45+
:mtc-version-z: 1.5.1

modules/migration-mtc-release-notes-1-5.adoc

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,8 @@ This release has the following new features and enhancements:
2525
[id="deprecated-features-1-5_{context}"]
2626
== Deprecated features
2727

28+
The following features are deprecated:
29+
2830
// https://issues.redhat.com/browse/MIG-623
2931
* {mtc-short} versions 1.2 and 1.3 are no longer supported.
3032
* The procedure for updating deprecated APIs has been removed from the troubleshooting section of the documentation because the `oc convert` command is deprecated.
@@ -37,3 +39,11 @@ This release has the following known issues:
3739
* PV resizing does not work as expected for AWS gp2 storage unless the `pv_resizing_threshold` is 42% or greater. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1973148[*BZ#1973148*])
3840
* If a migration fails, the migration plan does not retain custom PV settings for quiesced pods. You must manually roll back the migration, delete the migration plan, and create a new migration plan with your PV settings. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1784899[*BZ#1784899*])
3941
* Microsoft Azure storage is unavailable if you create more than 400 migration plans. The `MigStorage` custom resource displays the following message: `The request is being throttled as the limit has been reached for operation type`. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1977226[*BZ#1977226*])
42+
43+
[id="technical-changes-1-5_{context}"]
44+
== Technical changes
45+
46+
This release has the following technical changes:
47+
48+
* The legacy {mtc-full} Operator version 1.5.1 is installed manually on {product-title} versions 3.7 to 4.5.
49+
* The {mtc-full} Operator version 1.5.1 is installed on {product-title} versions 4.6 and later by using the Operator Lifecycle Manager.

0 commit comments

Comments
 (0)