Upgrading Che that uses namespace strategies other than 'per user'

This section describes how to upgrade Che that uses namespace strategies other than 'per user'.

Che intends to use Kubernetes secrets as a storage for all sensitive user data. One namespace per user simplifies the design of the workspaces. This is the reason why namespace strategies other than per user become deprecated. The deprecation process happens in two steps. In the First Step namespace strategies other than per user are allowed but not recommended. In the Second Step support for namespace strategies other than per user is going to be removed.

No automated upgrade support exists between First Step and Second Step for the installations where namespace strategies other than per user are used without losing data.
Prerequisites
  • Che configured with the namespace strategies other than per user.

  • Intention to use Che configured with the per user namespace strategies per user.

Upgrading Che and backing up user data

Procedure
  1. Notify all Che users about the upcoming data wipe.

    To back up the data, you can commit workspace configuration to an SCM server and use factories to restore it later.

  2. Re-install Che with per user namespace strategy.

Upgrading Che and losing user data

When Che is upgraded and user data is not backed up, workspace configuration and user preferences are going to be preserved but all runtime data will be wiped out.

Procedure
  1. Notify all Che users about the upcoming data wipe.

  2. Change namespace strategy to per user.

Upgrading without backing up user data has disadvantage. Original PVs with runtime data are going to be preserved and will no longer be used. This may lead to the waste of resources.