Skip to content

[enterprise-4.7] Fix for v4-7 to PR31675 #31696

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bobfuru wants to merge 1 commit into from
Closed

[enterprise-4.7] Fix for v4-7 to PR31675 #31696

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions modules/understanding-upgrade-channels.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,14 @@ endif::openshift-origin[]
ifndef::openshift-origin[]
[discrete]
== stable-{product-version} channel
While the `fast-{product-version}` channel contains releases as soon as their errata are published, releases are added to the `stable-{product-version}` channel after a delay. During this delay, data is collected from Red Hat SRE teams, Red Hat support services, and pre-production and production environments that participate in connected customer program about the stability of the release.

You can use the `stable-{product-version}` channel to upgrade from a previous minor version of {product-title}.
endif::openshift-origin[]
ifdef::openshift-origin[]
[discrete]
== stable-4 channel
Releases are added to the `stable-4` channel after passing all tests.

While the `fast-{product-version}` channel contains releases as soon as their errata are published, releases are added to the `stable-{product-version}` channel after a delay. During this delay, data is collected from Red Hat SRE teams, Red Hat support services, and pre-production and production environments that participate in connected customer program about the stability of the release. You can use the `stable-{product-version}` channel to upgrade from a previous minor version of {product-title}.
endif::openshift-origin[]
Expand Down Expand Up @@ -110,11 +118,7 @@ Red Hat will eventually provide supported update paths from any supported releas
endif::openshift-origin[]

ifdef::openshift-origin[]
The presence of an update recommendation in the `stable-4`
channel is a declaration that the update is fully supported while it is in the
channel. While releases will never be removed from the channel, update recommendations
that exhibit serious issues will be removed from the channel. Updates initiated
after the update recommendation has been removed might not be supported.
The presence of an update recommendation in the `stable-4` channel is a declaration that the update is fully supported while it is in the channel. While releases will never be removed from the channel, update recommendations that exhibit serious issues will be removed from the channel. Updates initiated after the update recommendation has been removed might not be supported.
endif::openshift-origin[]

ifndef::openshift-origin[]
Expand All @@ -124,6 +128,7 @@ ifndef::openshift-origin[]
The `fast-{product-version}` and `stable-{product-version}` channels present a choice between receiving general availability releases as soon as they are available or allowing Red Hat to control the rollout of those updates. If issues are detected during rollout or at a later time, upgrades to that version might be blocked in both the `fast-{product-version}` and `stable-{product-version}` channels, and a new version might be introduced that becomes the new preferred upgrade target.

Customers can improve this process by configuring pre-production systems on the `fast-{product-version}` channel, configuring production systems on the `stable-{product-version}` channel, and participating in the Red Hat connected customer program. Red Hat uses this program to observe the impact of updates on your specific hardware and software configurations. Future releases might improve or alter the pace at which updates move from the `fast-{product-version}` to the `stable-{product-version}` channel.
endif::openshift-origin[]

[discrete]
== Restricted network clusters
Expand All @@ -136,4 +141,3 @@ ifndef::openshift-origin[]

Your cluster is still supported if you change from the `stable-{product-version}` channel to the `fast-{product-version}` channel. Although you can switch to the `candidate-{product-version}` channel at any time, some releases in that channel might be unsupported release candidates. You can switch from the `candidate-{product-version}` channel to the `fast-{product-version}` channel if your current release is a general availability release. You can always switch from the `fast-{product-version}` channel to the `stable-{product-version}` channel, although if the current release was recently promoted to `fast-{product-version}` there can be a delay of up to a day for the release to be promoted to `stable-{product-version}`. If you change to a channel that does not include your current release, an alert displays and no updates can be recommended, but you can safely change back to your original channel at any point.
endif::openshift-origin[]