My test cluster is running release 4.5.4 and using the stable-4.5 channel. For deeper information about how Red Hat manages OpenShift update channels and releases, refer to The Ultimate Guide to OpenShift Release and Upgrade Process for Cluster Administrators. OpenShift update channels and upgrade paths contain many more nuances than I explain in this article. Only after a number of customers successfully run a given release without major incidents is an update added to the stable channel. Updates to OpenShift 4 are made available first in the fast channel. If I were in a hurry to update to OpenShift 4.6, or maybe to a very recent 4.5.x release, for example to get the fix for a critical bug that is affecting my production users, I might have to switch to a fast channel. Shame on me for leaving my cluster for so long without bug fixes and security updates! That is about to be corrected. That means that an early 4.6.z release might become updatable to 4.7 without passing through intermediate 4.6.z releases, using the web console.Īs I am still on 4.5 and I wish to follow the easy user interface (UI) provided by the web console, I have to first update to a newer 4.5.z release. OpenShift 4.6 changes the offerings so that the list of available update channels becomes dynamic and shows channels from new releases as they become available. Later z-stream releases add channels of the next minor release. The initial z-stream releases hard-code just their own update channels. It might be possible to update directly to an OpenShift 4.6.x release from the CLI, but up to OpenShift 4.5, the web console comes with a hardcoded list of candidate update channels. Why don't I see the channel for the next minor OpenShift release? I have not updated my test cluster since it was first installed a while ago.įigure 2: Available channels for updates.įor now, do not change the update channel. Mine is using the somewhat old 4.5.4 release, as shown in Figure 1. You should see a page that displays your cluster’s current update channel and OpenShift release. Open your OpenShift web console, log in with cluster administrator rights, and choose Administration->Cluster Settings. What is the current version of my OpenShift cluster? I hope to provide you with sufficient information to extrapolate to your specific scenario. You might start from a different release, target a different final release, and have to pass through different intermediate releases. SNO clusters will support updates when they become generally available.īecause the set of available updates and paths changes from time to time, you might not be able to follow the instructions in this article exactly as written. ![]() Later releases of OpenShift Container Platform will support single-node OpenShift (SNO) clusters, which follow a different design and installation process from CodeReady Containers. CodeReady Containers disables some of the cluster operators required for a successful update in order to reduce its hardware requirements, and the OpenShift update process was not designed to work with a single supervisor node, anyway. Note: Do not try to update a Red Hat CodeReady Containers (CRC) single-node cluster. If you have a test cluster that you were considering updating for some time and did not, for fear of the outcome, you can use the cluster now to follow the instructions from this article. If you need instructions about how to perform a cluster update using the CLI, please refer to the Red Hat OpenShift Container Platform product documentation and this article from the OpenShift knowledgebase. You can perform the entire cluster update process from the command-line interface (CLI) and automate it using Ansible playbooks, shell scripts, or whatever you like. OpenShift 4.6 includes significant improvements to its web console that solve most if not all of the gotchas that I demonstrate in this article. ![]() The update process, including web console pages and quirks, is mostly the same for earlier minor releases, for example a z-stream update of OpenShift 4.4. Note that you cannot skip a minor release during an update. ![]() Updating between two minor releases, from 4.y to 4.y+1.Note that you can skip z-stream releases during an update. Updating between two z-stream releases, from 4.y.z to 4.y.z+d.This article shows how two perform typical update scenarios, step-by-step: Still, updating OpenShift clusters can be scary the first time. OpenShift 4 makes the update process easy and provides a number of safety features to minimize the risk of a failed outcome. I include plenty of screenshots of actual updates from 4.5.4 to 4.5.17 and then to 4.6.4, so you know what to expect when you make these updates yourself. This article demonstrates two common scenarios for updating Red Hat OpenShift 4: to a newer z-stream release and to a newer minor release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |