mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
217 lines
6.8 KiB
Plaintext
217 lines
6.8 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * edge_computing/day_2_core_cnf_clusters/updating/update-api.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="update-selecting-the-target-release_{context}"]
|
|
= Selecting the target release
|
|
|
|
[role="_abstract"]
|
|
Use the link:https://access.redhat.com/labs/ocpupgradegraph/update_path[Red Hat {product-title} Update Graph] or the
|
|
link:https://github.com/openshift/cincinnati-graph-data/tree/master/channels[cincinnati-graph-data repository] to determine what release to update to.
|
|
|
|
[id="update-determining-available-z-streams_{context}"]
|
|
== Determining what z-stream updates are available
|
|
|
|
Before you can update to a new z-stream release, you need to know what versions are available.
|
|
|
|
[NOTE]
|
|
====
|
|
You do not need to change the channel when performing a z-stream update.
|
|
====
|
|
|
|
.Procedure
|
|
+
|
|
. Determine which z-stream releases are available.
|
|
Run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
Cluster version is 4.14.34
|
|
|
|
Upstream is unset, so the cluster will use an appropriate default.
|
|
Channel: stable-4.14 (available channels: candidate-4.14, candidate-4.15, eus-4.14, eus-4.16, fast-4.14, fast-4.15, stable-4.14, stable-4.15)
|
|
|
|
Recommended updates:
|
|
|
|
VERSION IMAGE
|
|
4.14.37 quay.io/openshift-release-dev/ocp-release@sha256:14e6ba3975e6c73b659fa55af25084b20ab38a543772ca70e184b903db73092b
|
|
4.14.36 quay.io/openshift-release-dev/ocp-release@sha256:4bc4925e8028158e3f313aa83e59e181c94d88b4aa82a3b00202d6f354e8dfed
|
|
4.14.35 quay.io/openshift-release-dev/ocp-release@sha256:883088e3e6efa7443b0ac28cd7682c2fdbda889b576edad626769bf956ac0858
|
|
----
|
|
|
|
[id="update-changing-channel-eus-to-eus_{context}"]
|
|
== Changing the channel for a Control Plane Only update
|
|
|
|
You must change the channel to the required version for a Control Plane Only update.
|
|
|
|
[NOTE]
|
|
====
|
|
You do not need to change the channel when performing a z-stream update.
|
|
====
|
|
|
|
.Procedure
|
|
+
|
|
. Determine the currently configured update channel by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusterversion -o=jsonpath='{.items[*].spec}' | jq
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
{
|
|
"channel": "stable-4.14",
|
|
"clusterID": "01eb9a57-2bfb-4f50-9d37-dc04bd5bac75"
|
|
}
|
|
----
|
|
|
|
. Change the channel to point to the new channel you want to update to by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade channel eus-4.16
|
|
----
|
|
|
|
. Confirm the updated channel by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusterversion -o=jsonpath='{.items[*].spec}' | jq
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
{
|
|
"channel": "eus-4.16",
|
|
"clusterID": "01eb9a57-2bfb-4f50-9d37-dc04bd5bac75"
|
|
}
|
|
----
|
|
|
|
[id="update-changing-channel-early-eus-to-eus_{context}"]
|
|
=== Changing the channel for an early EUS to EUS update
|
|
|
|
The update path to a brand new release of {product-title} is not available in either the EUS channel or the stable channel until 45 to 90 days after the initial GA of a minor release.
|
|
|
|
To begin testing an update to a new release, you can use the fast channel.
|
|
|
|
.Procedure
|
|
+
|
|
. Change the channel to `fast-<y+1>`.
|
|
For example, run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade channel fast-4.16
|
|
----
|
|
|
|
. Check the update path from the new channel.
|
|
Run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade
|
|
----
|
|
+
|
|
[source,terminal]
|
|
----
|
|
Cluster version is 4.15.33
|
|
|
|
Upgradeable=False
|
|
|
|
Reason: AdminAckRequired
|
|
Message: Kubernetes 1.28 and therefore {product-title} 4.16 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions.
|
|
|
|
Upstream is unset, so the cluster will use an appropriate default.
|
|
Channel: fast-4.16 (available channels: candidate-4.15, candidate-4.16, eus-4.15, eus-4.16, fast-4.15, fast-4.16, stable-4.15, stable-4.16)
|
|
|
|
Recommended updates:
|
|
|
|
VERSION IMAGE
|
|
4.16.14 quay.io/openshift-release-dev/ocp-release@sha256:6618dd3c0f5
|
|
4.16.13 quay.io/openshift-release-dev/ocp-release@sha256:7a72abc3
|
|
4.16.12 quay.io/openshift-release-dev/ocp-release@sha256:1c8359fc2
|
|
4.16.11 quay.io/openshift-release-dev/ocp-release@sha256:bc9006febfe
|
|
4.16.10 quay.io/openshift-release-dev/ocp-release@sha256:dece7b61b1
|
|
4.15.36 quay.io/openshift-release-dev/ocp-release@sha256:c31a56d19
|
|
4.15.35 quay.io/openshift-release-dev/ocp-release@sha256:f21253
|
|
4.15.34 quay.io/openshift-release-dev/ocp-release@sha256:2dd69c5
|
|
----
|
|
|
|
. Follow the update procedure to get to version 4.16 (<y+1> from version 4.15)
|
|
+
|
|
[NOTE]
|
|
====
|
|
You can keep your worker nodes paused between EUS releases even if you are using the fast channel.
|
|
====
|
|
|
|
. When you get to the required <y+1> release, change the channel again, this time to `fast-<y+2>`.
|
|
|
|
. Follow the EUS update procedure to get to the required <y+2> release.
|
|
|
|
[id="update-updating-y-stream_{context}"]
|
|
== Changing the channel for a y-stream update
|
|
|
|
In a y-stream update you change the channel to the next release channel.
|
|
|
|
[NOTE]
|
|
====
|
|
Use the stable or EUS release channels for production clusters.
|
|
====
|
|
|
|
.Procedure
|
|
+
|
|
. Change the update channel by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade channel stable-4.15
|
|
----
|
|
|
|
. Check the update path from the new channel.
|
|
Run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc adm upgrade
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
Cluster version is 4.14.34
|
|
|
|
Upgradeable=False
|
|
|
|
Reason: AdminAckRequired
|
|
Message: Kubernetes 1.27 and therefore {product-title} 4.15 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions.
|
|
|
|
Upstream is unset, so the cluster will use an appropriate default.
|
|
Channel: stable-4.15 (available channels: candidate-4.14, candidate-4.15, eus-4.14, eus-4.15, fast-4.14, fast-4.15, stable-4.14, stable-4.15)
|
|
|
|
Recommended updates:
|
|
|
|
VERSION IMAGE
|
|
4.15.33 quay.io/openshift-release-dev/ocp-release@sha256:7142dd4b560
|
|
4.15.32 quay.io/openshift-release-dev/ocp-release@sha256:cda8ea5b13dc9
|
|
4.15.31 quay.io/openshift-release-dev/ocp-release@sha256:07cf61e67d3eeee
|
|
4.15.30 quay.io/openshift-release-dev/ocp-release@sha256:6618dd3c0f5
|
|
4.15.29 quay.io/openshift-release-dev/ocp-release@sha256:7a72abc3
|
|
4.15.28 quay.io/openshift-release-dev/ocp-release@sha256:1c8359fc2
|
|
4.15.27 quay.io/openshift-release-dev/ocp-release@sha256:bc9006febfe
|
|
4.15.26 quay.io/openshift-release-dev/ocp-release@sha256:dece7b61b1
|
|
4.14.38 quay.io/openshift-release-dev/ocp-release@sha256:c93914c62d7
|
|
4.14.37 quay.io/openshift-release-dev/ocp-release@sha256:c31a56d19
|
|
4.14.36 quay.io/openshift-release-dev/ocp-release@sha256:f21253
|
|
4.14.35 quay.io/openshift-release-dev/ocp-release@sha256:2dd69c5
|
|
----
|