Re: [che-dev] Deprecate namespace strategies other than "per user"

[Sergii Kabashniuk <skabashn@xxxxxxxxxx>]

Hello, devs.

PR in che-server [1] and docs [2] has been merged in 7.31
PR in operator [3]  is on the way to merge in the same 7.31 version.

[1] https://github.com/eclipse/che/pull/19763 removes code that supports namespace strategies other than per-user

[2] https://github.com/eclipse/che-docs/pull/1983

[3] https://github.com/eclipse-che/che-operator/pull/818  Do not allow to upgrade che 7.31 or later to upgrade installation that configured with namespace strategies other than "per user" 

On Thu, Mar 25, 2021 at 2:19 PM Sergii Kabashniuk <skabashn@xxxxxxxxxx> wrote:

Hello, devs.

One and only one namespace per user simplifies a lot the design of the workspaces. We could assume then that every user configuration lives in his namespace. 

I would like to share plans about the deprecation of namespace strategies other than "per user"
The plan is following:

- At "Step One" we want to deprecate all namespace strategies other than "per user".
  That means only placeholder <username> or <userid> would be available for namespace strategies.
- At "Step One" we will add a warning with the notice about depreciation.
- At "Step One" we will provide some guides of what to do in case if someone is using namespace strategies other than "per user".

   Unfortunately, they would look like -  save all and create a new cluster.

- At "Step Two" only "per user" namespace strategy would be available.
- At "Step Two" those who have namespace strategies other than "per user" upgrade to the new version would be blocked in some form.

See more: Deprecate namespace strategies other than "per user" https://github.com/eclipse/che/issues/19365

--

Sergii Kabashniuk

Principal Software Engineer, DevTools 

Red Hat

skabashniuk@xxxxxxxxxx    

--

Sergii Kabashniuk

Principal Software Engineer, DevTools 

Red Hat

skabashniuk@xxxxxxxxxx