<commit_before>:_content-type: ASSEMBLY
[id="about-migrating-from-3-to-4"]
= About migrating from {product-title} 3 to 4
include::_attributes/common-attributes.adoc[]
:context: about-migrating-from-3-to-4

toc::[]

{product-title} 4 contains new technologies and functionality that result in a cluster that is self-managing, flexible, and automated. {product-title} 4 clusters are deployed and managed very differently from {product-title} 3.

The most effective way to migrate from {product-title} 3 to 4 is by using a CI/CD pipeline to automate deployments in an link:https://www.redhat.com/en/topics/devops/what-is-application-lifecycle-management-alm[application lifecycle management] framework.

If you do not have a CI/CD pipeline or if you are migrating stateful applications, you can use the {mtc-full} ({mtc-short}) to migrate your application workloads.

To successfully transition to {product-title} 4, review the following information:

xref:../migrating_from_ocp_3_to_4/planning-migration-3-4.adoc#planning-migration-3-4[Differences between {product-title} 3 and 4]::
* Architecture
* Installation and upgrade
* Storage, network, logging, security, and monitoring considerations

xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#about-mtc-3-4[About the {mtc-full}]::
* Workflow
* File system and snapshot copy methods for persistent volumes (PVs)
* Direct volume migration
* Direct image migration

xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#advanced-migration-options-3-4[Advanced migration options]::
* Automating your migration with migration hooks
* Using the {mtc-short} API
* Excluding resources from a migration plan
* Configuring the `MigrationController` custom resource for large-scale migrations
* Enabling automatic PV resizing for direct volume migration
* Enabling cached Kubernetes clients for improved performance

For new features and enhancements, technical changes, and known issues, see the xref:../migration_toolkit_for_containers/mtc-release-notes.adoc#mtc-release-notes[{mtc-short} release notes].<commit_msg>Add mkt statement and link to RHACM SOLP<commit_after>:_content-type: ASSEMBLY
[id="about-migrating-from-3-to-4"]
= About migrating from {product-title} 3 to 4
include::_attributes/common-attributes.adoc[]
:context: about-migrating-from-3-to-4

toc::[]

{product-title} 4 contains new technologies and functionality that result in a cluster that is self-managing, flexible, and automated. {product-title} 4 clusters are deployed and managed very differently from {product-title} 3.

The most effective way to migrate from {product-title} 3 to 4 is by using a CI/CD pipeline to automate deployments in an link:https://www.redhat.com/en/topics/devops/what-is-application-lifecycle-management-alm[application lifecycle management] framework.

If you do not have a CI/CD pipeline or if you are migrating stateful applications, you can use the {mtc-full} ({mtc-short}) to migrate your application workloads.

You can use Red Hat Advanced Cluster Management for Kubernetes to help you import and manage your {product-title} 3 clusters easily, enforce policies, and redeploy your applications. Take advantage of the link:https://www.redhat.com/en/engage/free-access-redhat-e-202202170127[free subscription] to use Red Hat Advanced Cluster Management to simplify your migration process.

To successfully transition to {product-title} 4, review the following information:

xref:../migrating_from_ocp_3_to_4/planning-migration-3-4.adoc#planning-migration-3-4[Differences between {product-title} 3 and 4]::
* Architecture
* Installation and upgrade
* Storage, network, logging, security, and monitoring considerations

xref:../migrating_from_ocp_3_to_4/about-mtc-3-4.adoc#about-mtc-3-4[About the {mtc-full}]::
* Workflow
* File system and snapshot copy methods for persistent volumes (PVs)
* Direct volume migration
* Direct image migration

xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#advanced-migration-options-3-4[Advanced migration options]::
* Automating your migration with migration hooks
* Using the {mtc-short} API
* Excluding resources from a migration plan
* Configuring the `MigrationController` custom resource for large-scale migrations
* Enabling automatic PV resizing for direct volume migration
* Enabling cached Kubernetes clients for improved performance

For new features and enhancements, technical changes, and known issues, see the xref:../migration_toolkit_for_containers/mtc-release-notes.adoc#mtc-release-notes[{mtc-short} release notes].
{'fraction_non_alphanumeric': 0.09001097694840834, 'fraction_numerical': 0.016904500548847422, 'mean_word_length': 5.545977011494253, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 3, 'lorem ipsum': 0, 'www.': 3, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3630284', 'n_tokens_mistral': 1364, 'n_tokens_neox': 1295, 'n_words': 451}