Moving stuff between Kubernetes clusters can be a pain in the butt. You have to do this when:<\/p>\n
Migrating work between clusters requires some thought and planning, and good solid processes. Specifically, the migration from OpenShift 3.x to OpenShift 4.x requires<\/em> a parallel upgrade, because there is no in-place upgrade available for all of the new goodies in RHEL CoreOS<\/a> (the underlying infrastructure of the cluster). OpenShift 4.2<\/a> released recently, so we thought it would be good timing to put our migration thoughts down here. However, the advice below is generally good for any Kubernetes cluster parallel upgrade or other migration.<\/p>\n <\/p>\n This video<\/a>, talking about the upstream OKD, is pretty good, and these slides<\/a> cover a lot of important stuff. If you’re a Red Hat customer, contact your account team – they can talk you through the platform updates and discuss your situation in detail. Be sure to talk about what you’re currently using OpenShift for, and what you plan to use it for, and also any pain points you have with what you’re doing today.<\/p>\n The big OpenShift changes come in three big chunks: security (including the CoreOS changes), operations (specifically operators and finding ways to lessen the need for esoteric infrastructure knowledge), and enablement of developers<\/a>.<\/p>\n Get your infrastructure\/operations people, your architects, and your DevOps people in a room (ideally with a whiteboard or two), and talk through the plan. Talk about if you want help migrating, and if so, how much. OpenShift 4.2 comes with a migration tool that will do at least some of the work for you. The migration tool can automate your migration, project-by-project, which is pretty slick. Check out this video:<\/p>\nThe Plan<\/h2>\n
1. Understand what’s new and fundamentally different for OpenShift 4.<\/h3>\n
2. Make the Plan!<\/h3>\n