This is a cache of https://docs.okd.io/latest/migrating_from_ocp_3_to_4/about-migrating-from-3-to-4.html. It is a snapshot of the page at 2024-11-26T19:31:57.253+0000.
About migrating from OKD 3 to 4 | Migrating from version 3 to 4 | OKD 4
  1. Documentation
×

About migrating from OKD 3 to 4

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

The most effective way to migrate from OKD 3 to 4 is by using a CI/CD pipeline to automate deployments in an application lifecycle management framework.

If you do not have a CI/CD pipeline or if you are migrating stateful applications, you can use the Migration Toolkit for Containers (MTC) to migrate your application workloads.

You can use Red Hat Advanced Cluster Management for Kubernetes to help you import and manage your OKD 3 clusters easily, enforce policies, and redeploy your applications. Take advantage of the free subscription to use Red Hat Advanced Cluster Management to simplify your migration process.

To successfully transition to OKD 4, review the following information:

Differences between OKD 3 and 4

  • Architecture

  • Installation and upgrade

  • Storage, network, logging, security, and monitoring considerations

About the Migration Toolkit for Containers

  • Workflow

  • File system and snapshot copy methods for persistent volumes (PVs)

  • Direct volume migration

  • Direct image migration

Advanced migration options

  • Automating your migration with migration hooks

  • Using the MTC 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 MTC release notes.