Verify that all OpenShift Dev Spaces components are running the new version and that the platform is functional so that you can confirm the upgrade succeeded before notifying developers.
Before you begin
- You have an active
oc session with administrative permissions to the OpenShift cluster. See OpenShift CLI.
Procedure
-
Verify that the OpenShift Dev Spaces Operator CSV shows the expected version and
Succeeded phase:
$ CSV_COLUMNS='NAME:.metadata.name,PHASE:.status.phase,VERSION:.spec.version'
$ oc get csv -n openshift-devspaces \
-o "custom-columns=${CSV_COLUMNS}"
Expected output:
NAME PHASE VERSION
devspacesoperator.v3.29.0 Succeeded 3.29.0
-
Verify that the
CheCluster custom resource reports Active phase and the correct version:
$ oc get checluster devspaces \
-n openshift-devspaces \
-o jsonpath='Phase: {.status.chePhase}, Version: {.status.cheVersion}'
Expected output:
Phase: Active, Version: 3.29.0
-
Verify that all OpenShift Dev Spaces pods in the
openshift-devspaces namespace are running and ready:
$ oc get pods -n openshift-devspaces
All pods should show Running status with all containers ready.
-
Verify that the OpenShift Dev Spaces dashboard is accessible:
$ oc get checluster devspaces \
-n openshift-devspaces \
-o jsonpath='{.status.cheURL}'
Open the returned URL in a browser and confirm the login page loads.
-
Verify that the Dev Workspace Operator is running the expected version:
$ oc get csv -n <devworkspace_operator_namespace> \
-o custom-columns='NAME:.metadata.name,PHASE:.status.phase' \
| grep devworkspace
The Dev Workspace Operator CSV should show version 0.42.0 and the Succeeded phase.
Replace <devworkspace_operator_namespace> with the project where the Dev Workspace Operator is installed. For OpenShift Dev Spaces, this is typically openshift-devspaces. For a standalone Dev Workspace Operator installation, this is openshift-operators.
-
Start a test workspace from the OpenShift Dev Spaces dashboard to confirm that workspaces function correctly after the upgrade.