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

Possibility to customize cheHost when running on OpenShift 4 as the default route may not be suitable

XMLWordPrintable

      1. Proposed title of this feature request
      Possibility to customize cheHost when running on OpenShift 4 as the default route may not be suitable

      2. What is the nature and description of the request?
      When deploying Red Hat CodeReady Workspaces it is not possible to customize cheHost, meaning that the route for exposing service will always be "codeready-codeready.apps.<clusterid>.<domain>" on OpenShift Container Platform 4. This is not suitable in lots of environments as a customized cheHost would be required to easily expose the CodeReady Workspaces (such as "codeready.<domain>" or similar).

      3. Why does the customer need this? (List the business requirements here)
      Customers use ".apps.<clusterid>.<domain>" only for core OpenShift services. Every other workload is exposed using ".<domain>". So Red Hat CodeReady Workspace does not comply with this policy which does generate challenges and actually does prevent adoption of the product. This is why cheHost needs to be exposed in the custom resource to allow customization and have any route suitable applyed.

      4. How would the customer like to achieve this? (List the functional requirements here)
      Exposing the cheHost parameter in the custom resource to allow modification of this value at install time and have it put in place accordingly (in all configruatione, etc.).

      5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
      N/A

              abazko Anatolii Bazko
              rhn-support-sreber Simon Reber
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: