MIG-1107 MTC 1.7 Release Notes #43766
Conversation
openshift-ci
bot
added
the
size/M
✅ Deploy Preview for osdocs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
|
||
| The following features are deprecated: | ||
|
|
||
| * {mtc-short} version 1.5 and 1.6 are deprecated. Support for them will be removed in a future version. |
There was a problem hiding this comment.
1.5 and 1.6 are not deprecated unless there is some formal definition for this that I'm unaware of. We intend to fully support this until 1.8 is released when support will be dropped.
|
@eriknelson My understanding of "deprecated" is exactly what you said: We still support it, but we know that in the future we will stop supporting it. |
|
@stoobie We've never used that language for our supported currentRelease - 1 channel, I'd prefer not to introduce it now should it discourage users from using it or suggest that is in any way not supported at the same level that 1.7 is. |
|
@eriknelson I made the change you requested, but here's my experience with the definition of Deprecated (In RHV): https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/release_notes/index#Deprecated_Features_RHV |
|
@stillalearner: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
| The {mtc-full} ({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 OpenShift Container Platform Life Cycle Policy_ |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Thanks, @darshan-nagaraj . I made the change.
In the future, I suggest using the Add a suggestion
button, because it makes the diffs in your suggestion much clearer.
There was a problem hiding this comment.
@stoobie Noted. Thanks for letting me know.
| @@ -6,12 +6,16 @@ include::_attributes/common-attributes.adoc[] | |||
|
|
|||
| toc::[] | |||
|
|
|||
| The release notes for {mtc-full} ({mtc-short}) describe new features and enhancements, deprecated features, and known issues. | |||
|
|
|||
| The {mtc-full} ({mtc-short}) enables you to migrate application workloads between {product-title} clusters at the granularity of a namespace. | |||
There was a problem hiding this comment.
Remove {mtc-full} because it is already abbreviated in the first sentence.
| // Module included in the following assemblies: | ||
| // | ||
| // * migration_toolkit_for_containers/mtc-release-notes.adoc | ||
|
|
There was a problem hiding this comment.
:_content-type: REFERENCE
stoobie
force-pushed
the
MIG-1107
branch
6 times, most recently
from
5f3e3d5
to
d778d93
Compare
| :_content-type: REFERENCE | ||
| [id="migration-mtc-release-notes-1-7_{context}"] | ||
| = {mtc-full} 1.7 release notes | ||
|
|
There was a problem hiding this comment.
You need some introductory text between the H1 and H2.
There was a problem hiding this comment.
Will not fix. I hope this isn't a blocker.
There was a problem hiding this comment.
@RichardHoch, please consider opening a follow-up PR to add this heading. It's a mod docs and Jupiter requirement that's not quite a blocker and not quite enough for a bug.
|
|
||
| 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. |
There was a problem hiding this comment.
"Operator" is always capitalized.
|
|
||
| * 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 using the `crane tunnel-api` command. |
There was a problem hiding this comment.
This sounds like it should be "by using." Per the ISG:
! using noun
To avoid ambiguity, replace this gerund with either "by using" or "that uses".
|
|
||
| This release has the following known issues: | ||
|
|
||
| * On {product-title} 3.10, the `MigrationController` pod takes too long to restart. The Bugzilla report contains a workaround. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1986796[*BZ#1986796*]) |
There was a problem hiding this comment.
I am confused by this line. 3.10 is EOL.
|
|
||
| * On {product-title} 3.10, the `MigrationController` pod takes too long to restart. The Bugzilla report contains a workaround. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1986796[*BZ#1986796*]) | ||
| * `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]. |
There was a problem hiding this comment.
Consider specifying what also needs to be in the same availability zone. I assume that it's the cluster, but I am not sure based on the current context.
There was a problem hiding this comment.
Will not fix. I hope this isn't high priority.
|
/cherrypick enterprise-4.10 |
|
/cherrypick enterprise-4.11 |
|
@kalexand-rh: new pull request created: #44013 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@kalexand-rh: new pull request created: #44014 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR addresses https://issues.redhat.com/browse/MIG-1107.
This applies to:
enterprise-4.10 and later
Preview:
https://deploy-preview-43766--osdocs.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/mtc-release-notes.html
Updated:
MTC 1.7 Release Notes