-
Bug
-
Resolution: Done
-
Minor
-
None
-
OpenShift 4.7 Async, OpenShift 4.8 Async, OpenShift 4.9 Async
-
-
- Document URL
-
https://docs.openshift.com/container-platform/4.9/logging/cluster-logging-upgrading.html
https://docs.openshift.com/container-platform/4.8/logging/cluster-logging-upgrading.html
https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-upgrading.html
https://docs.openshift.com/container-platform/4.9/logging/cluster-logging-deploying.html
https://docs.openshift.com/container-platform/4.8/logging/cluster-logging-deploying.html
https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-deploying.html
-
- Section Number and Name
-
Updating from cluster logging in OpenShift Container Platform 4.6 or earlier to OpenShift Logging 5.x
-
-
- Describe the issue:
-
It's possible to read the next phrase:
~~~
In the Change Subscription Update Channel window, select 5.0 or stable-5.x and click Save.
~~~
Also
~~~
Verify that the Red Hat OpenShift Logging Operator version is 5.0.x or 5.x.x.
~~~
And
~~~
Verify that the log collector is updated to 5.0 or 5.x:
~~~
And
~~~
Verify that the log visualizer is updated to 5.0 or 5.x using the Kibana CRD:
~~~
Then, 5.0 is not supported more, then, it shouldn't be mentioned. It could be changed "5.0 or 5.x" for any supported version.
Also, when it's said stable-5.x, now, it's possible to use only "stable", if you choose stable, when a new version is released, it's updated to this version without needing to modify the subscription channel.
Then, it would be great to indicate stable or stable-5.x and the difference since this is a question asked a lot of times.
-
-
- Suggestions for improvement
Do the most generic possible content and independent of the versions, only referencing to the supported version that they are visible in the matrix.
- Suggestions for improvement
-
-
-
- Additional information:
-
This is happening also in the "Installing Logging" section where it's continually referenced 5.0 or stable-5.x. The same 2 improvements commented in the description are applicable to this section.
Please, review specific references to versions in the documentation, in special to 5.0.