How the upgrade works
Understand what happens during a Che upgrade so that you can plan the timing, communicate downtime expectations, and verify the result.
When you upgrade Che, the Operator handles the server component upgrade automatically. You do not need to manually update individual pods or configurations. The Operator:
-
Replaces the Che 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
CheClustercustom 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
Che 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.
Kubernetes or OpenShift version compatibility
Che 7.120 is supported on Kubernetes or OpenShift {platforms-ver}. Before you upgrade Che, verify that your Kubernetes or OpenShift cluster version is within the supported range.