About migrating from OKD 3 to 4
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.
To successfully transition to OKD 4, review the following information:
Architecture
Storage, network, logging, security, and monitoring considerations
About the Migration Toolkit for Containers
File system and snapshot copy methods for persistent volumes (PVs)
Direct volume migration
Using the MTC API
Excluding resources from a migration plan
Configuring the custom resource for large-scale migrations
Enabling cached Kubernetes clients for improved performance