Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1895

Drop namespace strategies other than "per user"

    XMLWordPrintable

Details

    • 1
    • False
    • False
    • Release Notes
    • Hide
      = {prod-short} is Switching to `per-user` namespace strategy

      All namespace strategies except the `per-user` strategy are unsupported.

      This results in:

      * Improving security.
      * Better administration control over the assigned resource to a user using namespace quotas.
      * Elimination of the need to duplicate sensitive information using Kubernetes secrets, as with the `per-workspace strategy`.
      Show
      = {prod-short} is Switching to `per-user` namespace strategy All namespace strategies except the `per-user` strategy are unsupported. This results in: * Improving security. * Better administration control over the assigned resource to a user using namespace quotas. * Elimination of the need to duplicate sensitive information using Kubernetes secrets, as with the `per-workspace strategy`.

    Description

      Is your task related to a problem? Please describe.

      When switching to DevWorkspace we would like to drop support for namespace strategies other than "per user".
      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.
      Describe the solution you'd like

      At the "deprecation" stage we need to reflect that fact on documentation and add a warning when someone wants to use it.
      Describe alternatives you've considered

      Remove support without "deprecation" stage

      https://github.com/eclipse/che/issues/19536

      Attachments

        Issue Links

          Activity

            People

              mmaler@redhat.com Michal Maléř
              ffloreth@redhat.com Fabrice Flore-Thébault
              Sergii Kabashniuk
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: