You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{product-title} versions 4.7 and 4.8 both support OpenShift Logging versions 5.0 and 5.1.
8
9
10
+
To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7 or 4.8. Then, you update the following operators:
9
11
10
-
After updating the {product-title} cluster from 4.6 to 4.7, you can update the OpenShift Elasticsearch Operator and Cluster Logging Operator from 4.6 to 5.0.
12
+
* From Elasticsearch Operator 4.x to OpenShift Elasticsearch Operator 5.x
13
+
* From Cluster Logging Operator 4.x to Red Hat OpenShift Logging Operator 5.x
11
14
12
-
[NOTE]
13
-
====
14
-
In OpenShift Logging 5.0 and later, the Cluster Logging Operator is called Red Hat OpenShift Logging Operator.
15
-
====
15
+
To upgrade from a previous version of OpenShift Logging to the current version, you update OpenShift Elasticsearch Operator and Red Hat OpenShift Logging Operator to their current versions.
16
16
17
17
// The following include statements pull in the module files that comprise
18
18
// the assembly. Include any combination of concept, procedure, or reference
19
19
// modules required to cover the user story. You can also include other
<1> You must specify the `openshift-logging` Namespace.
241
-
<2> Specify `5.0` or `stable` as the channel. `stable` is the latest 5.x released code.
241
+
<2> Specify `5.0` or `stable-5.<x>` as the channel. `stable-5.<x>` is the latest released code for the version number you specify with `x`.
242
242
<3> Specify `redhat-operators`. If your {product-title} cluster is installed on a restricted network, also known as a disconnected cluster, specify the name of the CatalogSource object you created when you configured the Operator Lifecycle Manager (OLM).
243
243
+
244
244
[source,terminal]
@@ -269,7 +269,7 @@ $ oc get csv -n openshift-logging
= Updating from cluster logging in {product-title} 4.6 or earlier to OpenShift Logging 5.x
4
3
5
-
[id="cluster-logging-updating-logging_{context}"]
6
-
= Updating OpenShift Logging
4
+
{product-title} 4.7 made the following name changes:
7
5
8
-
After updating the {product-title} cluster, you can update from cluster logging 4.6 to Red Hat OpenShift Logging 5.0 by changing the subscription for the OpenShift Elasticsearch Operator and the Cluster Logging Operator.
6
+
* The _cluster logging_ feature became the _Red Hat OpenShift Logging_ 5.x product.
7
+
* The _Cluster Logging_ Operator became the _Red Hat OpenShift Logging_ Operator.
8
+
* The _Elasticsearch_ Operator became _OpenShift Elasticsearch_ Operator.
9
9
10
-
[NOTE]
11
-
====
12
-
In OpenShift Logging 5.0 and later, the Cluster Logging Operator is called Red Hat OpenShift Logging Operator.
13
-
====
10
+
To upgrade from cluster logging in {product-title} version 4.6 and earlier to OpenShift Logging 5.x, you update the {product-title} cluster to version 4.7 or 4.8. Then, you update the following operators:
14
11
15
-
When you update:
16
-
17
-
* You must update the OpenShift Elasticsearch Operator before updating the Cluster Logging Operator.
18
-
* You must update both the OpenShift Elasticsearch Operator and the Cluster Logging Operator.
19
-
+
20
-
Kibana is unusable when the OpenShift Elasticsearch Operator has been updated but the Cluster Logging Operator has not been updated.
21
-
+
22
-
If you update the Cluster Logging Operator before the OpenShift Elasticsearch Operator, Kibana does not update and the Kibana custom resource (CR) is not created. To work around this problem, delete the Cluster Logging Operator pod. When the Cluster Logging Operator pod redeploys, the Kibana CR is created.
12
+
* From Elasticsearch Operator 4.x to OpenShift Elasticsearch Operator 5.x
13
+
* From Cluster Logging Operator 4.x to Red Hat OpenShift Logging Operator 5.x
23
14
24
15
[IMPORTANT]
25
16
====
26
-
Upgrade your cluster logging version to 4.6 before updating to Red Hat OpenShift Logging 5.0.
17
+
You must update the OpenShift Elasticsearch Operator _before_ you update the Red Hat OpenShift Logging Operator. You must also update _both_ Operators to the same version.
27
18
====
28
19
20
+
If you update the operators in the wrong order, Kibana does not update and the Kibana custom resource (CR) is not created. To work around this problem, you delete the Red Hat OpenShift Logging Operator pod. When the Red Hat OpenShift Logging Operator pod redeploys, it creates the Kibana CR and Kibana becomes available again.
21
+
29
22
.Prerequisites
30
23
31
-
* Update the {product-title} cluster from 4.6 to 4.7.
24
+
* The {product-title} version is 4.7 or later.
32
25
33
-
* Make sure the OpenShift Logging status is healthy:
34
-
+
26
+
* The OpenShift Logging status is healthy:
35
27
** All pods are `ready`.
36
28
** The Elasticsearch cluster is healthy.
37
29
38
-
* Back up your Elasticsearch and Kibana data.
30
+
* Your Elasticsearch and Kibana data is backed up.
39
31
40
32
.Procedure
41
33
@@ -49,11 +41,11 @@ Upgrade your cluster logging version to 4.6 before updating to Red Hat OpenShift
49
41
50
42
.. Click *Subscription* -> *Channel*.
51
43
52
-
.. In the *Change Subscription Update Channel* window, select *5.0* and click *Save*.
44
+
.. In the *Change Subscription Update Channel* window, select *5.0* or *stable-5.1* and click *Save*.
53
45
54
46
.. Wait for a few seconds, then click *Operators* -> *Installed Operators*.
55
47
+
56
-
Verify that the OpenShift Elasticsearch Operator version is 5.0.x.
48
+
Verify that the OpenShift Elasticsearch Operator version is 5.x.x.
57
49
+
58
50
Wait for the *Status* field to report *Succeeded*.
59
51
@@ -67,11 +59,11 @@ Wait for the *Status* field to report *Succeeded*.
67
59
68
60
.. Click *Subscription* -> *Channel*.
69
61
70
-
.. In the *Change Subscription Update Channel* window, select *5.0* and click *Save*.
62
+
.. In the *Change Subscription Update Channel* window, select *5.0* or *stable-5.1* and click *Save*.
71
63
72
64
.. Wait for a few seconds, then click *Operators* -> *Installed Operators*.
73
65
+
74
-
Verify that the Red Hat OpenShift Logging Operator version is 5.0.x.
66
+
Verify that the Red Hat OpenShift Logging Operator version is 5.0.x or 5.1.x.
75
67
+
76
68
Wait for the *Status* field to report *Succeeded*.
0 commit comments