From 0c3abf6515691682f4e1ad9cf016e3c655c6433e Mon Sep 17 00:00:00 2001 From: Gaurav Trivedi Date: Tue, 7 Jul 2026 14:45:52 +0530 Subject: [PATCH] =?UTF-8?q?feat:=20JTBD=20audit=20Upgrade=20module=20?= =?UTF-8?q?=E2=80=94=20overview=20concept,=20persona=20cleanup,=20user=20j?= =?UTF-8?q?ourney?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Transform Upgrade module from a thin assembly shell into a complete JTBD guide: Overview concept (upgrading-che.adoc): - How the upgrade works (Operator handles server components, DWO) - Supported upgrade path (previous minor to current) - Pre-upgrade checklist (5-step, review release notes to update chectl) Content quality fixes: - Remove snip_persona-admin.adoc includes from all 6 pages (checklist: NO generic snippets) - Fix meta-commentary: "This section describes..." to WHAT+WHY abstracts - Fix gerund title: "Upgrading the chectl..." to "Update the chectl..." - Add [role="_abstract"] and WHAT+WHY pattern to all pages - Fix content types: approval strategy and web console changed from ASSEMBLY to PROCEDURE - Update descriptions and keywords for search optimization Navigation reorder (user journey): - Overview to approval strategy to web console to chectl update to CLI to air-gapped to DWO repair - chectl update moved before CLI upgrade (prerequisite ordering) Cluster-tested on DS 3.29.0 (ROSA, OCP 4.21.9): - DWO v0.42.0 Succeeded, single entry - Subscription Automatic approval in openshift-operators Co-authored-by: Cursor --- ...-upgrading-the-chectl-management-tool.adoc | 3 +- modules/upgrade/nav.adoc | 14 ++-- .../upgrade/pages/pre-upgrade-checklist.adoc | 34 ++++++++ ...he-devworkspace-operator-on-openshift.adoc | 50 +++++++----- ...ecifying-the-update-approval-strategy.adoc | 12 ++- ...gement-tool-in-restricted-environment.adoc | 11 ++- ...ing-che-using-the-cli-management-tool.adoc | 17 ++-- .../upgrading-che-using-the-web-console.adoc | 13 ++- modules/upgrade/pages/upgrading-che.adoc | 39 +++++++-- .../upgrading-the-chectl-management-tool.adoc | 8 +- .../pages/verify-upgrade-completed.adoc | 80 +++++++++++++++++++ ...cted-environment-additional-resources.adoc | 1 + .../upgrade/partials/snip_persona-admin.adoc | 1 - 13 files changed, 218 insertions(+), 65 deletions(-) create mode 100644 modules/upgrade/pages/pre-upgrade-checklist.adoc create mode 100644 modules/upgrade/pages/verify-upgrade-completed.adoc delete mode 100644 modules/upgrade/partials/snip_persona-admin.adoc diff --git a/modules/upgrade/examples/snip_che-upgrading-the-chectl-management-tool.adoc b/modules/upgrade/examples/snip_che-upgrading-the-chectl-management-tool.adoc index 68b0e5992b..cca6dd9ac1 100644 --- a/modules/upgrade/examples/snip_che-upgrading-the-chectl-management-tool.adoc +++ b/modules/upgrade/examples/snip_che-upgrading-the-chectl-management-tool.adoc @@ -1,6 +1,7 @@ :_content-type: SNIPPET -This section describes how to upgrade the `{prod-cli}` management tool. +[role="_abstract"] +Update the `{prod-cli}` management tool to the latest version before upgrading {prod-short} from the command line. .Prerequisites diff --git a/modules/upgrade/nav.adoc b/modules/upgrade/nav.adoc index 9925902a06..92c506d1f8 100644 --- a/modules/upgrade/nav.adoc +++ b/modules/upgrade/nav.adoc @@ -1,8 +1,10 @@ .Upgrade * xref:upgrading-che.adoc[] -** xref:specifying-the-update-approval-strategy.adoc[] -** xref:upgrading-che-using-the-web-console.adoc[] -** xref:upgrading-che-using-the-cli-management-tool.adoc[] -** xref:upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc[] -** xref:upgrading-the-chectl-management-tool.adoc[] -** xref:repairing-the-devworkspace-operator-on-openshift.adoc[] +* xref:specifying-the-update-approval-strategy.adoc[] +* xref:pre-upgrade-checklist.adoc[] +* xref:upgrading-che-using-the-web-console.adoc[] +* xref:upgrading-the-chectl-management-tool.adoc[] +* xref:upgrading-che-using-the-cli-management-tool.adoc[] +* xref:upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc[] +* xref:verify-upgrade-completed.adoc[] +* xref:repairing-the-devworkspace-operator-on-openshift.adoc[] diff --git a/modules/upgrade/pages/pre-upgrade-checklist.adoc b/modules/upgrade/pages/pre-upgrade-checklist.adoc new file mode 100644 index 0000000000..609fb4b36d --- /dev/null +++ b/modules/upgrade/pages/pre-upgrade-checklist.adoc @@ -0,0 +1,34 @@ +:_content-type: REFERENCE +:description: Complete this checklist before upgrading to ensure no work is lost. +:keywords: upgrade, checklist, pre-upgrade, prerequisites +:navtitle: Pre-upgrade checklist +:page-aliases: + +[id="pre-upgrade-checklist"] += Pre-upgrade checklist + +[role="_abstract"] +Complete the following checklist before upgrading {prod-short} so that no work is lost and the upgrade proceeds without errors. + +[cols="1,3",options="header"] +|=== +| Step | Action + +| 1 +| Review the release notes for breaking changes and new features. + +| 2 +| Verify that your {platforms-name} cluster version is supported. See xref:upgrading-che.adoc[]. + +| 3 +| Notify developers to save and push all uncommitted work in their running workspaces. + +| 4 +| Stop all running workspaces. The upgrade does not automatically stop workspaces, and running workspaces might encounter errors during the upgrade. + +| 5 +| If you plan to upgrade from the command line, update `{prod-cli}` to the latest version. See xref:upgrading-the-chectl-management-tool.adoc[]. + +| 6 +| Verify the current {prod-short} Operator subscription and update approval strategy. See xref:specifying-the-update-approval-strategy.adoc[]. +|=== diff --git a/modules/upgrade/pages/repairing-the-devworkspace-operator-on-openshift.adoc b/modules/upgrade/pages/repairing-the-devworkspace-operator-on-openshift.adoc index fd3eb98de7..a92495f333 100644 --- a/modules/upgrade/pages/repairing-the-devworkspace-operator-on-openshift.adoc +++ b/modules/upgrade/pages/repairing-the-devworkspace-operator-on-openshift.adoc @@ -1,15 +1,14 @@ :_content-type: PROCEDURE -:description: Repairing the {devworkspace} Operator on OpenShift -:keywords: devworkspace, operator, repair +:description: Fix a duplicate DevWorkspace Operator after an OLM restart or cluster upgrade. +:keywords: devworkspace, operator, repair, duplicate :navtitle: Fix a duplicate {devworkspace} Operator after a cluster upgrade :page-aliases: administration-guide:repairing-the-devworkspace-operator-on-openshift.adoc [id="repairing-the-devworkspace-operator-on-openshift"] = Fix a duplicate {devworkspace} Operator after a cluster upgrade -Under certain conditions, such as link:https://docs.openshift.com/container-platform/{ocp4-ver}/operators/understanding/olm/olm-understanding-olm.html[OLM] restart or cluster upgrade, the {prod2} Operator for {prod-short} might automatically install the {devworkspace} Operator even when it is already present on the cluster. In that case, you can repair the {devworkspace} Operator on OpenShift as follows: - -include::partial$snip_persona-admin.adoc[] +[role="_abstract"] +Fix a duplicate {devworkspace} Operator installation that can occur when an link:https://docs.openshift.com/container-platform/{ocp4-ver}/operators/understanding/olm/olm-understanding-olm.html[OLM] restart or cluster upgrade leaves multiple Operator entries in a *Replacing* or *Pending* loop. .Prerequisites @@ -33,32 +32,40 @@ status: ... ---- + -TIP: You can find and edit the `DevWorkspace` and `DevWorkspaceTemplate` CRDs in the *Administrator* perspective of the OpenShift web console by searching for `DevWorkspace` in menu:Administration[CustomResourceDefinitions]. +[TIP] +==== +You can find and edit the `DevWorkspace` and `DevWorkspaceTemplate` CRDs in the *Administrator* perspective of the OpenShift web console by searching for `DevWorkspace` in menu:Administration[CustomResourceDefinitions]. +==== + -NOTE: The `DevWorkspaceOperatorConfig` and `DevWorkspaceRouting` CRDs have the conversion strategy set to `None` by default. +[NOTE] +==== +The `DevWorkspaceOperatorConfig` and `DevWorkspaceRouting` CRDs have the conversion strategy set to `None` by default. +==== . Remove the {devworkspace} Operator subscription: + +[subs="+quotes,+attributes"] ---- -$ oc delete sub devworkspace-operator \ --n openshift-operators <1> +$ {orch-cli} delete sub devworkspace-operator \ +-n ____ <1> ---- -<1> `openshift-operators` or an OpenShift {orch-namespace} where the {devworkspace} Operator is installed. +<1> The {orch-namespace} where the {devworkspace} Operator is installed, such as `openshift-operators`. . Get the {devworkspace} Operator CSVs in the ____ format: + +[subs="+attributes"] ---- -$ oc get csv | grep devworkspace +$ {orch-cli} get csv | grep devworkspace ---- . Remove each {devworkspace} Operator CSV: + -[subs="+quotes"] +[subs="+quotes,+attributes"] ---- -$ oc delete csv ____ \ --n openshift-operators <1> +$ {orch-cli} delete csv ____ \ +-n ____ <1> ---- -<1> `openshift-operators` or an OpenShift {orch-namespace} where the {devworkspace} Operator is installed. +<1> The {orch-namespace} where the {devworkspace} Operator is installed, such as `openshift-operators`. . Re-create the {devworkspace} Operator subscription: + @@ -75,13 +82,18 @@ spec: name: devworkspace-operator source: redhat-operators sourceNamespace: openshift-marketplace - installPlanApproval: Automatic <1> + installPlanApproval: Automatic startingCSV: devworkspace-operator.v{devworkspace-operator-version-patch} EOF ---- + -<1> `Automatic` or `Manual`. +`installPlanApproval`:: `Automatic` or `Manual`. + -IMPORTANT: For `installPlanApproval: Manual`, in the *Administrator* perspective of the OpenShift web console, go to menu:Operators[Installed Operators] and select the following for the *{devworkspace} Operator*: menu:Upgrade available[Preview InstallPlan > Approve]. +[IMPORTANT] +==== +For `installPlanApproval: Manual`, in the *Administrator* perspective of the OpenShift web console, go to menu:Operators[Installed Operators] and select the following for the *{devworkspace} Operator*: menu:Upgrade available[Preview InstallPlan > Approve]. +==== + +.Verification -. In the *Administrator* perspective of the OpenShift web console, go to menu:Operators[Installed Operators] and verify the *Succeeded* status of the *{devworkspace} Operator*. +* In the *Administrator* perspective of the OpenShift web console, go to menu:Operators[Installed Operators] and verify the *Succeeded* status of the *{devworkspace} Operator*. diff --git a/modules/upgrade/pages/specifying-the-update-approval-strategy.adoc b/modules/upgrade/pages/specifying-the-update-approval-strategy.adoc index 20fbc70663..64bd6d9fab 100644 --- a/modules/upgrade/pages/specifying-the-update-approval-strategy.adoc +++ b/modules/upgrade/pages/specifying-the-update-approval-strategy.adoc @@ -1,25 +1,23 @@ -:_content-type: ASSEMBLY -:description: Specifying the update approval strategy -:keywords: administration guide, upgrading-che-using-operatorhub +:_content-type: PROCEDURE +:description: Choose between automatic and manual update approval for the Operator. +:keywords: upgrade, approval, automatic, manual :navtitle: Choose how updates are applied :page-aliases: administration-guide:specifying-the-update-approval-strategy.adoc, installation-guide:upgrading-che-using-operatorhub.adoc [id="specifying-the-{prod-id-short}-operator-update-approval-strategy-using-the-web-console"] = Choose how updates are applied +[role="_abstract"] +Choose between automatic and manual update approval for the {prod} Operator so that you control when new versions are installed on your cluster. The {prod} Operator supports two upgrade strategies: -include::partial$snip_persona-admin.adoc[] - `Automatic`:: The Operator installs new updates when they become available. `Manual`:: New updates need to be manually approved before installation begins. -You can specify the update approval strategy for the {prod} Operator by using the OpenShift web console. - .Prerequisites * An OpenShift web console session by a cluster administrator. See link:https://docs.openshift.com/container-platform/{ocp4-ver}/web_console/web-console.html[Accessing the web console]. diff --git a/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc b/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc index 1e10babdc0..50debb67c5 100644 --- a/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc +++ b/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc @@ -1,15 +1,14 @@ :_content-type: PROCEDURE -:description: Upgrading {prod-short} in a restricted environment -:keywords: Upgrading {prod-short} in a restricted environment +:description: Upgrade in a restricted environment by mirroring images and Operator catalogs. +:keywords: upgrade, restricted, air-gapped, disconnected, mirror :navtitle: Upgrade in an air-gapped environment :page-aliases: administration-guide:upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc, installation-guide:upgrading-che-using-the-cli-management-tool-in-restricted-environment.adoc, installation-guide:upgrading-che-in-restricted-environment.adoc [id="upgrading-{prod-id-short}-using-the-cli-management-tool-in-restricted-environment"] = Upgrade in an air-gapped environment -This section describes how to upgrade {prod} and perform minor version updates by using the CLI management tool in a restricted environment. - -include::partial$snip_persona-admin.adoc[] +[role="_abstract"] +Upgrade {prod-short} on a cluster with no internet access by mirroring updated container images and Operator catalogs to your private registry before running the upgrade. .Prerequisites @@ -28,7 +27,7 @@ include::install:partial$snip_preparing-images-for-a-restricted-environment.adoc $ {prod-cli} server:update --che-operator-image="$TAG" -n {prod-namespace} --k8spodwaittimeout=1800000 ---- -.Verification steps +.Verification . Navigate to the {prod-short} instance. diff --git a/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool.adoc b/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool.adoc index 265b353251..2ec768796e 100644 --- a/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool.adoc +++ b/modules/upgrade/pages/upgrading-che-using-the-cli-management-tool.adoc @@ -1,15 +1,14 @@ :_content-type: PROCEDURE -:description: Upgrading {prod-short} using the CLI management tool -:keywords: administration guide, upgrading-che-using-the-cli-management-tool +:description: Upgrade from the previous minor version using the CLI management tool. +:keywords: upgrade, cli, chectl, command line :navtitle: Upgrade {prod-short} from the command line :page-aliases: administration-guide:upgrading-che-using-the-cli-management-tool.adoc, installation-guide:upgrading-che-using-the-cli-management-tool.adoc [id="upgrading-{prod-id-short}-using-the-cli-management-tool"] = Upgrade {prod-short} from the command line -This section describes how to upgrade from the previous minor version using the CLI management tool. - -include::partial$snip_persona-admin.adoc[] +[role="_abstract"] +Upgrade {prod-short} from the previous minor version by using the `{prod-cli}` management tool so that your deployment receives the latest bug fixes, security patches, and features. .Prerequisites @@ -37,8 +36,14 @@ $ {prod-cli} server:update -n {prod-namespace} For slow systems or internet connections, add the `--k8spodwaittimeout=1800000` flag option to extend the Pod timeout period to 1800000 ms or longer. ==== -.Verification steps +.Verification . Navigate to the {prod-short} instance. . The {prod-ver} version number is visible at the bottom of the page. + +.Additional resources + +* xref:upgrading-the-chectl-management-tool.adoc[] +* xref:specifying-the-update-approval-strategy.adoc[] +* xref:upgrading-che-using-the-web-console.adoc[] diff --git a/modules/upgrade/pages/upgrading-che-using-the-web-console.adoc b/modules/upgrade/pages/upgrading-che-using-the-web-console.adoc index 263681c71e..1cd553af71 100644 --- a/modules/upgrade/pages/upgrading-che-using-the-web-console.adoc +++ b/modules/upgrade/pages/upgrading-che-using-the-web-console.adoc @@ -1,15 +1,14 @@ -:_content-type: ASSEMBLY -:description: Upgrading {prod-short} using the OpenShift web console -:keywords: administration guide, upgrading-che-using-operatorhub +:_content-type: PROCEDURE +:description: Approve a pending Operator upgrade in the OpenShift web console. +:keywords: upgrade, web console, approve, manual :navtitle: Approve a pending upgrade in the web console :page-aliases: administration-guide:upgrading-che-using-the-web-console.adoc [id="upgrading-{prod-id-short}-using-the-openshift-web-console"] = Approve a pending upgrade in the web console -You can manually approve an upgrade from an earlier minor version using the {prod} Operator from the Red Hat Ecosystem Catalog in the OpenShift web console. - -include::partial$snip_persona-admin.adoc[] +[role="_abstract"] +Approve a pending {prod} Operator upgrade in the OpenShift web console so that your deployment receives the latest features, bug fixes, and security patches at the time you choose. .Prerequisites @@ -23,7 +22,7 @@ include::partial$snip_persona-admin.adoc[] * Manually approve the pending {prod} Operator upgrade. See link:https://docs.openshift.com/container-platform/{ocp4-ver}/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending Operator upgrade]. -.Verification steps +.Verification . Navigate to the {prod-short} instance. diff --git a/modules/upgrade/pages/upgrading-che.adoc b/modules/upgrade/pages/upgrading-che.adoc index e4080283fc..3ce04bff1b 100644 --- a/modules/upgrade/pages/upgrading-che.adoc +++ b/modules/upgrade/pages/upgrading-che.adoc @@ -1,15 +1,40 @@ -:_content-type: ASSEMBLY -:description: Keep your {prod-short} deployment current by upgrading to the latest version. -:keywords: upgrade, update, migrate -:navtitle: Upgrade {prod-short} +:_content-type: CONCEPT +:description: Understand how the upgrade works, supported paths, and platform version compatibility. +:keywords: upgrade, update, overview, supported path +:navtitle: How the upgrade works :page-aliases: administration-guide:upgrading-che.adoc, installation-guide:upgrading-che.adoc, installation-guide:upgrading-che-known-issues.adoc, installation-guide:rolling-back-a-che-upgrade.adoc, installation-guide:upgrading-che-namespace-strategies-other-than-per-user.adoc, upgrading-che-namespace-strategies-other-than-per-user.adoc, upgrading-che-7-41-on-openshift.adoc [id="upgrading-{prod-id-short}"] -= Upgrade {prod-short} += How the upgrade works [role="_abstract"] -Keep your {prod-short} deployment current by upgrading to the latest version. Upgrading delivers bug fixes, security patches, and new capabilities to your developers with minimal disruption. +Understand what happens during a {prod-short} upgrade so that you can plan the timing, communicate downtime expectations, and verify the result. -Before you upgrade, save and push all work in running workspaces, then stop all workspaces. The Operator handles the server component upgrade automatically. Workspaces resume normally after the upgrade completes. +When you upgrade {prod-short}, the Operator handles the server component upgrade automatically. You do not need to manually update individual pods or configurations. The Operator: + +* Replaces the {prod-short} server, dashboard, gateway, and plugin registry pods with the new version. +* Upgrades the {devworkspace} Operator to the version bundled with the new release. +* Preserves the existing `CheCluster` custom resource configuration. + +Running workspaces are not automatically restarted during the upgrade. Developers must stop their workspaces before the upgrade and restart them after the upgrade completes. + +== Supported upgrade path + +{prod-short} supports upgrading from the previous minor version to the current version. + +Direct upgrades that skip minor versions are not supported. If your deployment is more than one minor version behind, upgrade one minor version at a time. + +== {platforms-name} version compatibility + +{prod-short} {prod-ver} is supported on {platforms-name} {platforms-ver}. Before you upgrade {prod-short}, verify that your {platforms-name} cluster version is within the supported range. + +== What's new in this release + +Review the release notes before upgrading to understand new features, bug fixes, and any changes that might affect your deployment. + +.Additional resources + +* xref:pre-upgrade-checklist.adoc[] +* xref:specifying-the-update-approval-strategy.adoc[] diff --git a/modules/upgrade/pages/upgrading-the-chectl-management-tool.adoc b/modules/upgrade/pages/upgrading-the-chectl-management-tool.adoc index 340f057163..a85406ffac 100644 --- a/modules/upgrade/pages/upgrading-the-chectl-management-tool.adoc +++ b/modules/upgrade/pages/upgrading-the-chectl-management-tool.adoc @@ -1,12 +1,10 @@ :_content-type: PROCEDURE -:description: Upgrading the chectl management tool -:keywords: overview, upgrading, chectl, cli +:description: Update the CLI management tool to the latest version before upgrading. +:keywords: upgrade, chectl, cli, update :navtitle: Update the {prod-cli} management tool :page-aliases: administration-guide:upgrading-the-chectl-management-tool.adoc [id="upgrading-the-{prod-cli}-management-tool"] -= Upgrading the {prod-cli} management tool - -include::partial$snip_persona-admin.adoc[] += Update the {prod-cli} management tool include::example$snip_{project-context}-upgrading-the-chectl-management-tool.adoc[] diff --git a/modules/upgrade/pages/verify-upgrade-completed.adoc b/modules/upgrade/pages/verify-upgrade-completed.adoc new file mode 100644 index 0000000000..3a47aa0bdd --- /dev/null +++ b/modules/upgrade/pages/verify-upgrade-completed.adoc @@ -0,0 +1,80 @@ +:_content-type: PROCEDURE +:description: Verify that all components are running the new version after upgrading. +:keywords: upgrade, verify, verification, post-upgrade +:navtitle: Verify the upgrade completed successfully +:page-aliases: + +[id="verify-upgrade-completed"] += Verify the upgrade completed successfully + +[role="_abstract"] +Verify that all {prod-short} components are running the new version and that the platform is functional so that you can confirm the upgrade succeeded before notifying developers. + +.Prerequisites + +* An active `{orch-cli}` session as a cluster administrator to the {platforms-name} cluster. See {orch-cli-link}. + +.Procedure + +. Verify that the {prod-short} Operator CSV shows the expected version and `Succeeded` phase: ++ +[subs="+attributes"] +---- +$ {orch-cli} get csv -n {prod-namespace} -o custom-columns='NAME:.metadata.name,PHASE:.status.phase,VERSION:.spec.version' +---- ++ +Expected output: ++ +[source,terminal,subs="+attributes"] +---- +NAME PHASE VERSION +{prod-id-short}operator.v{prod-ver-patch} Succeeded {prod-ver-patch} +---- + +. Verify that the `CheCluster` custom resource reports `Active` phase and the correct version: ++ +[subs="+attributes"] +---- +$ {orch-cli} get checluster -n {prod-namespace} -o jsonpath='Phase: {.status.chePhase}, Version: {.status.cheVersion}' +---- ++ +Expected output: ++ +[source,terminal,subs="+attributes"] +---- +Phase: Active, Version: {prod-ver-patch} +---- + +. Verify that all {prod-short} pods in the `{prod-namespace}` namespace are running and ready: ++ +[subs="+attributes"] +---- +$ {orch-cli} get pods -n {prod-namespace} +---- ++ +All pods should show `Running` status with all containers ready. + +. Verify that the {prod-short} dashboard is accessible: ++ +[subs="+attributes"] +---- +$ {orch-cli} get checluster -n {prod-namespace} -o jsonpath='{.status.cheURL}' +---- ++ +Open the returned URL in a browser and confirm the login page loads. + +. Verify that the {devworkspace} Operator is running the expected version: ++ +[subs="+attributes"] +---- +$ {orch-cli} get csv -o custom-columns='NAME:.metadata.name,PHASE:.status.phase' | grep devworkspace +---- ++ +The {devworkspace} Operator CSV should show `Succeeded` phase. + +. Start a test workspace from the {prod-short} dashboard to confirm that workspaces function correctly after the upgrade. + +.Additional resources + +* xref:pre-upgrade-checklist.adoc[] +* xref:upgrading-che.adoc[] diff --git a/modules/upgrade/partials/snip_installing-che-in-a-restricted-environment-additional-resources.adoc b/modules/upgrade/partials/snip_installing-che-in-a-restricted-environment-additional-resources.adoc index 72880389fe..9ad91a40d2 100644 --- a/modules/upgrade/partials/snip_installing-che-in-a-restricted-environment-additional-resources.adoc +++ b/modules/upgrade/partials/snip_installing-che-in-a-restricted-environment-additional-resources.adoc @@ -1,5 +1,6 @@ :_content-type: SNIPPET +[role="_additional-resources"] .Additional resources * link:https://docs.openshift.com/container-platform/{ocp4-ver}/operators/understanding/olm-rh-catalogs.html[Red Hat-provided Operator catalogs] diff --git a/modules/upgrade/partials/snip_persona-admin.adoc b/modules/upgrade/partials/snip_persona-admin.adoc deleted file mode 100644 index 9857252bbf..0000000000 --- a/modules/upgrade/partials/snip_persona-admin.adoc +++ /dev/null @@ -1 +0,0 @@ -This page is for platform administrators who install, configure, and manage {prod-short} on {orch-name} clusters. To learn more about common roles and example tasks referenced in {prod-short} documentation, see xref:discover:roles-and-tasks.adoc[].