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

Document as Known Issue: Namespace restriction in OSD and ROSA

    XMLWordPrintable

Details

    • False
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, User Experience
    • Hide
      = Namespace restriction for {osd} and ROSA

      Currently, there is a restriction for {osd} and ROSA: {prod-short} must not be deployed to the `openshift-workspaces` namespace.

      .Workaround

      * Use another namespace when deploying {prod-short} on {osd} and ROSA.
      Show
      = Namespace restriction for {osd} and ROSA Currently, there is a restriction for {osd} and ROSA: {prod-short} must not be deployed to the `openshift-workspaces` namespace. .Workaround * Use another namespace when deploying {prod-short} on {osd} and ROSA.
    • Documented as Known Issue

    Description

      Keep this issue open to ensure the presence of a Known Issue item in the Release Notes.

       

      This bug has been opened to evaluate and consider changing the default project throughout CRW from `openshift-workspaces` to something else.

      For OSD/ROSA, the namespace must not be `openshift-workspaces`. It can be any name except that one.

      There are many instances of the `openshift-workspaces` namespace in procedures, code blocks, and examples:
      Admin Guide = 15 matches
      End-User Guide = 9 matches
      Installation Guide = 7 matches

      At least some are mentions of it as a default.

      For example, in our CRW Admin Guide here, it says that If installed using crwctl, the default CodeReady Workspaces project is `openshift-workspaces`.

       

       

      Attachments

        Issue Links

          Activity

            People

              rhn-support-mleonov Max Leonov
              rhn-support-mleonov Max Leonov
              Max Leonov Max Leonov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: