UKCloud for Red Hat OpenShift life cycle and patch management
This article outlines the lifecycle of UKCloud-supported OpenShift releases, along with UKCloud's approach to patching existing OpenShift environments so that you can effectively plan, deploy and support your infrastructure. The purpose of this article is to provide as much transparency as possible, but UKCloud may make exceptions from the process described should the need arise.
Administrators and operators of the UKCloud for Red Hat OpenShift service.
Red Hat's official versioning for their OpenShift Container Platform is X.Y where X indicates the major version and Y indicates a minor version.
Although Red Hat officially fully supports each major X version of the OpenShift Container Platform for five years, as a service provider, this duration is too long for UKCloud to ensure the highest levels of security, performance and features. As such, UKCloud will officially support the current (X.Y) and previous minor version (X.Y-1). As minor versions are released roughly every six months, this provides the assurance that your environments will be fully supported by UKCloud for a minimum of twelve months.
To illustrate this, the green shaded areas in the image below, show which versions UKCloud would support for different released versions.
Upgrades of major X and minor Y versions
Currently, UKCloud does not offer in-place upgrades between major versions. Customers can trigger minor version upgrades inside the cluster at any time, providing total flexibility to upgrade at a convenient time.
We require customers to stay on UKCloud-supported versions, so ask that upgrades are done in a timely manner to stay on a Y-1 release. For more information on performing updates and what happens if customers aren't on Y-1, see Supported customer update strategy for version 4 clusters.
Patching within current version
Red Hat routinely releases patches for vulnerabilities or issues identified within the currently supported version of OpenShift. UKCloud will release these patches to the stable update channel when they are confirmed to be fit for production workloads.
If you find a problem with this article, click Improve this Doc to make the change yourself or raise an issue in GitHub. If you have an idea for how we could improve any of our services, send an email to email@example.com.