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

RN-Mention:Document the setup needed for syncing Che settings to devworkspace namespaces

XMLWordPrintable

    • False
    • False
    • Hide
      = Synchronization of the {prod-short} server settings to workspaces using the {devworkspace} engine

      Before this update, when using the {devworkspace} engine, {prod-short} workspaces were missing required configuration settings, such as proxy or self-signed certificates. With this update, the settings stored by the {prod-short} server are propagated to the workspaces.
      Show
      = Synchronization of the {prod-short} server settings to workspaces using the {devworkspace} engine Before this update, when using the {devworkspace} engine, {prod-short} workspaces were missing required configuration settings, such as proxy or self-signed certificates. With this update, the settings stored by the {prod-short} server are propagated to the workspaces.

      Reference: https://github.com/eclipse-che/che-operator/pull/1027

      This feature adds the ability to sync settings to the workspace namespaces of the users.

      The new controller watches namespaces (or projects on OpenShift). If a namespace has appropriate label (org.eclipse.che/workspace-namespace-owner-uid), it is considered a user workspace namespace and is synced to.

      The value of the label is supposed to be the UID of the user. On OpenShift, this is the UID of the user object and on Kubernetes, the UID of the user as obtained from the OAuth token of the configured OIDC provider.

              skabashn Sergii Kabashniuk
              mmaler@redhat.com Michal Maléř
              Lukas Krejci, Sergii Kabashniuk
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: