此内容没有您所选择的语言版本。

Chapter 1. About migrating from OpenShift Container Platform 3 to 4


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

The most effective way to migrate from OpenShift Container Platform 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 OpenShift Container Platform 4, review the following information:

Differences between OpenShift Container Platform 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
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.